What it may solve
Drive9 workspace and durable evidence components for DeepSeek Harness
Imported third-party catalog description; not a Registry verification conclusion.Drive9 workspace and durable evidence components for DeepSeek Harness
Author: drive9-ai · Tools & Capabilities · Catalog snapshot: 2026-09-19Canonical semantic path
Drive9 workspace and durable evidence components for DeepSeek Harness
Imported third-party catalog description; not a Registry verification conclusion.— stars · 82 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: 3 stars, 14 commits, 0 forks, and 0 watches; latest commit 2026-08-14.
Conclusion: Resolved npm release 0.1.0, published 2026-08-14, license Apache-2.0.
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: contains credential or token handling code, may create or modify files, may access the network. No predefined elevated-risk condition was triggered; this is not proof of safety.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: @drive9/drive9-dsh@0.1.0; SHA-256: cb1457f9b580f963334d0715d27dbd74651501217e6f306c32e6805cd2b0b7a8.
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 @drive9/drive9-dsh. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
@drive9/drive9-dshAnalyzed 0.1.0github:drive9-ai/drive9-dshExact version not resolved