What it may solve
Owner-governed long-term memory bundle for DeepSeek Harness
Imported third-party catalog description; not a Registry verification conclusion.Owner-governed long-term memory bundle for DeepSeek Harness
Author: mianyoubiaoqing · Memory · Catalog snapshot: 2026-09-19Canonical semantic path
Owner-governed long-term memory bundle for DeepSeek Harness
Imported third-party catalog description; not a Registry verification conclusion.— stars · 543 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: 8 stars, 67 commits, 0 forks, and 0 watches; latest commit 2026-08-21.
Conclusion: Resolved npm release 0.0.1-alpha.3, published 2026-08-21, 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 2 code capabilities: contains credential or token handling code, 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: @mistymoon/dsh-mmem@0.0.1-alpha.3; SHA-256: e62c44d454b9d95b9bc000ee202013a470ffb84a6133d5fe96fc3a77520b9cdc.
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 @mistymoon/dsh-mmem. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
@mistymoon/dsh-mmemAnalyzed 0.0.1-alpha.3github:mianyoubiaoqing/dsh-MmemExact version not resolved