What it may solve
Local Git-backed long-term memory for DeepSeek Harness with hybrid CJK/English retrieval, cited context, transactional sync, previews, and rollback.
Imported third-party catalog description; not a Registry verification conclusion.Local Git-backed long-term memory for DeepSeek Harness with hybrid CJK/English retrieval, cited context, transactional sync, previews, and rollback.
Author: seriousz158 · Memory · Catalog snapshot: 2026-09-19Canonical semantic path
Local Git-backed long-term memory for DeepSeek Harness with hybrid CJK/English retrieval, cited context, transactional sync, previews, and rollback.
Imported third-party catalog description; not a Registry verification conclusion.180 stars · 694 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: 184 stars, 96 commits, 2 forks, and 0 watches; latest commit 2026-09-01.
Conclusion: Resolved npm release 0.8.1, published 2026-08-24, license MIT.
Conclusion: Compatibility verification did not pass: the DSH process exited because the plugin imports an API that this DSH version does not export. 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: may read environment variables, may create or modify files, 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: dsh-git-memory@0.8.1; SHA-256: 0e1ab00f3cb2108ef94241466003da256daa5649e48b6818595ad2ae87b97226.
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-memory. 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-git-memoryAnalyzed 0.8.1github:seriousz158/dsh-memoryExact version not resolved