What it may solve
Cross-session agent messaging for DeepSeek Harness with session discovery, offline delivery, delivery receipts, and sender-session navigation.
Imported third-party catalog description; not a Registry verification conclusion.Cross-session agent messaging for DeepSeek Harness with session discovery, offline delivery, delivery receipts, and sender-session navigation.
Author: GengDaPeng · Sessions & Messages · Catalog snapshot: 2026-09-19Canonical semantic path
Cross-session agent messaging for DeepSeek Harness with session discovery, offline delivery, delivery receipts, and sender-session navigation.
Imported third-party catalog description; not a Registry verification conclusion.6 stars · 410 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: 6 stars, 36 commits, 0 forks, and 0 watches; latest commit 2026-08-31.
Conclusion: Resolved npm release 1.6.0, published 2026-08-31, 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 bounded static scan found none of its predefined risk signals. This is not proof of safety.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-agent-message@1.6.0; SHA-256: 1fae30f306809a46b525053bf7d1848f4e2f05ccca49df00cd6796a12d02d9ef.
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-agent-message. 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-agent-messageAnalyzed 1.6.0github:GengDaPeng/dsh-agent-messageExact version not resolved