What it may solve
Persistent AI memory backed by a local Obsidian/Codex vault: five obsidian_memory_* read/write/search tools plus a sidebar vault browser.
Imported third-party catalog description; not a Registry verification conclusion.Persistent AI memory backed by a local Obsidian/Codex vault: five obsidian_memory_* read/write/search tools plus a sidebar vault browser.
Author: detongz · Memory · Catalog snapshot: 2026-09-19Canonical semantic path
Persistent AI memory backed by a local Obsidian/Codex vault: five obsidian_memory_* read/write/search tools plus a sidebar vault browser.
Imported third-party catalog description; not a Registry verification conclusion.detongz/dsh-client-ui-obsidian-memory
14 stars · 1039 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: 15 stars, 27 commits, 0 forks, and 0 watches; latest commit 2026-08-17.
Conclusion: Resolved npm release 0.3.2, published 2026-08-17, license MIT.
Conclusion: Compatibility verification did not pass: the DSH process exited during startup. 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: declares a prepare script, normally used when building or publishing the package, may read environment variables, 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-client-ui-obsidian-memory@0.3.2; SHA-256: dcf7b14157841248ddc4ea4f488588b7212ea7ec3659d41cbf7d00246cf7fff0.
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-client-ui-obsidian-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-client-ui-obsidian-memoryAnalyzed 0.3.2github:detongz/dsh-client-ui-obsidian-memoryExact version not resolved