What it may solve
Writes local JSONL summaries of per-turn tool counts and coarse verification signals without storing prompts, tool arguments, or result text.
Imported third-party catalog description; not a Registry verification conclusion.Writes local JSONL summaries of per-turn tool counts and coarse verification signals without storing prompts, tool arguments, or result text.
Author: 030611 · Security & Permissions · Catalog snapshot: 2026-09-19Canonical semantic path
Writes local JSONL summaries of per-turn tool counts and coarse verification signals without storing prompts, tool arguments, or result text.
Imported third-party catalog description; not a Registry verification conclusion.030611/dsh-verification-receipt
4 stars · 618 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: 5 stars, 11 commits, 0 forks, and 0 watches; latest commit 2026-09-03.
Conclusion: Resolved npm release 0.1.0, published 2026-08-14, 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 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-verification-receipt@0.1.0; SHA-256: 8179996503491b2e8cc757eeaf779e92995c7d3bace732f76e56c6d0812a1a0d.
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-verification-receipt. 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-verification-receiptAnalyzed 0.1.0github:030611/dsh-verification-receiptExact version not resolved