Track DeepSeek Harness's own releases and update in one click: reads the npm dist-tags and the GitHub changelog, shows every change between the running build and the target, grades the risk, then hands the install to a detached helper that backs the current install up with an atomic rename, runs npm, verifies what landed, relaunches, and rolls back when the new build does not come up.
Author: zhengjy01 · Development & Runtime · Catalog snapshot: 2026-09-19Canonical semantic path
Track DeepSeek Harness's own releases and update in one click: reads the npm dist-tags and the GitHub changelog, shows every change between the running build and the target, grades the risk, then hands the install to a detached helper that backs the current install up with an atomic rename, runs npm, verifies what landed, relaunches, and rolls back when the new build does not come up.
Imported third-party catalog description; not a Registry verification conclusion.0 stars · 99 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19Active analysis coverage 4/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, 1 commits, 0 forks, and 0 watches; latest commit 2026-09-13.
Conclusion: Resolved npm release 0.1.0, published 2026-09-13, 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 6 code capabilities: declares a prepare script, normally used when building or publishing the package, contains credential or token handling code, may read environment variables, 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: @zhengjunyao/dsh-updater@0.1.0; SHA-256: 39662b16e2171b83db9e38429c647d0d61aa10799e9b9db2dec24a1f69514ca0.
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-updater. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
@zhengjunyao/dsh-updaterAnalyzed 0.1.0github:zhengjy01/dsh-updaterExact version not resolved