What it may solve
A friendly status and context-pressure companion for DeepSeek Harness Web
Imported third-party catalog description; not a Registry verification conclusion.A friendly status and context-pressure companion for DeepSeek Harness Web
Author: gjnzsu · Memory · Catalog snapshot: 2026-09-19Canonical semantic path
A friendly status and context-pressure companion for DeepSeek Harness Web
Imported third-party catalog description; not a Registry verification conclusion.— stars · 740 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: 0 stars, 30 commits, 0 forks, and 0 watches; latest commit 2026-08-17.
Conclusion: Resolved npm release 0.1.1, published 2026-08-17, 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 bounded static scan found none of its predefined risk signals. This is not proof of safety.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-companion@0.1.1; SHA-256: 6785c5d3e3b32e948da83646915ed40d4c8d4ba8feae9280654038680c21bc55.
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-companion. 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-companionAnalyzed 0.1.1github:gjnzsu/dsh-companionExact version not resolved