What it may solve
The Blue launcher with a prepacked, pinned dsh runtime
Imported third-party catalog description; not a Registry verification conclusion.The Blue launcher with a prepacked, pinned dsh runtime
Author: dsh-blue · UI Enhancements · Catalog snapshot: 2026-09-19Canonical semantic path
The Blue launcher with a prepacked, pinned dsh runtime
Imported third-party catalog description; not a Registry verification conclusion.— stars · 1522 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: 18 stars, 668 commits, 1 forks, and 0 watches; latest commit 2026-09-02.
Conclusion: Resolved npm release 0.1.1-rc.2, published 2026-08-30, 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 found 5 characteristics that need attention: may read environment variables, may create or modify files, may access the network, may start external processes, may execute shell commands. This is a bounded automated observation, not a determination of malicious intent.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: @dsh-blue/blue-cli@0.1.1-rc.2; SHA-256: 95d83660a938b1327444ecb491e8102947f5066d6ea1268ce2ee6d423f023440.
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-blue/blue-cli. 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-blue/blue-cliAnalyzed 0.1.1-rc.2github:dsh-blue/blueExact version not resolved