What it may solve
LLM auto-approval for sandbox escalation requests, with presets and a fail-closed fallback.
Imported third-party catalog description; not a Registry verification conclusion.LLM auto-approval for sandbox escalation requests, with presets and a fail-closed fallback.
Author: SeverusZh · Security & Permissions · Catalog snapshot: 2026-09-19Canonical semantic path
LLM auto-approval for sandbox escalation requests, with presets and a fail-closed fallback.
Imported third-party catalog description; not a Registry verification conclusion.3 stars · 622 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19Active analysis coverage 5/5. Historical chains are retained but do not count toward current coverage.
Conclusion: The source structure check completed without finding a structural issue.
Conclusion: The GitHub repository is reachable and not archived. Public data: 4 stars, 27 commits, 0 forks, and 0 watches; latest commit 2026-09-04.
Conclusion: Resolved npm release 0.5.0, published 2026-09-04, license MIT.
Conclusion: Compatibility verification passed. Installation, profile loading, and sustained startup all completed. Test environment: DSH 0.1.6-alpha.2, web profile.
Conclusion: This bounded audit reported 0 known vulnerabilities. It covers only the locked versions and audit source; zero reports is not proof of safety.
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Conclusion: The scan observed 3 code capabilities: may create or modify files, may access the network, may start external processes. No predefined elevated-risk condition was triggered; this is not proof of safety.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-yolo-mode@0.5.0; SHA-256: f4b51fc77d58d246edd1d3c92aff515e73f8c52f38325c4b707ad2cbbf5f523b.
Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.
Describe your task in a DSH conversation and mention dsh-yolo-mode. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
dsh-yolo-modeAnalyzed 0.5.0github:SeverusZh/dsh-yolo-modeExact version not resolved