What it may solve
Safe, local workspace checkpoints and two-phase restore for DeepSeek Harness
Imported third-party catalog description; not a Registry verification conclusion.Safe, local workspace checkpoints and two-phase restore for DeepSeek Harness
Author: zjukop · Tools & Capabilities · Catalog snapshot: 2026-09-19Canonical semantic path
Safe, local workspace checkpoints and two-phase restore for DeepSeek Harness
Imported third-party catalog description; not a Registry verification conclusion.— stars · 189 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 could not be confirmed as reachable.
Conclusion: Resolved npm release 0.1.0, published 2026-08-15, 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 1 code capabilities: may create or modify files. No predefined elevated-risk condition was triggered; this is not proof of safety.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-time-machine@0.1.0; SHA-256: fd694e763409439cd6a5e2d2ec97cb5fcf3721fe5735c8306dc713ce800b89ff.
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-time-machine. 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-time-machineAnalyzed 0.1.0github:zjukop/dsh-time-machineExact version not resolved