What it may solve
Layered file memory for DeepSeek Harness with workspace-scoped USER/MEMORY notes, background consolidation, and hybrid session recall.
Imported third-party catalog description; not a Registry verification conclusion.Layered file memory for DeepSeek Harness with workspace-scoped USER/MEMORY notes, background consolidation, and hybrid session recall.
Author: aqsk-BLG · Memory · Catalog snapshot: 2026-09-19Canonical semantic path
Layered file memory for DeepSeek Harness with workspace-scoped USER/MEMORY notes, background consolidation, and hybrid session recall.
Imported third-party catalog description; not a Registry verification conclusion.2 stars · 433 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, 13 commits, 0 forks, and 0 watches; latest commit 2026-08-19.
Conclusion: Resolved npm release 1.3.2, published 2026-08-20, 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 4 code capabilities: contains credential or token handling code, may read environment variables, 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: dsh-file-memory@1.3.2; SHA-256: 30adccb73c071e533ad41db87e1d6c752d5ad0056e0a6a96bea8b8ed02f14284.
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-file-memoryAnalyzed 1.3.2github:aqsk-BLG/dsh-memoryExact version not resolved