What it may solve
Branch-based message editing, reroll, retry, and a version timeline.
Imported third-party catalog description; not a Registry verification conclusion.Branch-based message editing, reroll, retry, and a version timeline.
Author: Moeblack · Sessions & Messages · Catalog snapshot: 2026-09-19Canonical semantic path
Branch-based message editing, reroll, retry, and a version timeline.
Imported third-party catalog description; not a Registry verification conclusion.49 stars · 2346 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: 49 stars, 7 commits, 19 forks, and 0 watches; latest commit 2026-08-16.
Conclusion: Resolved npm release 0.2.3, published 2026-08-16, 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 1 code capabilities: 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-message-edit@0.2.3; SHA-256: af8c80a6613374802a208a6180600eed36fce1c19fafb41f7f275e3eacd8545c.
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-message-edit. 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-message-editAnalyzed 0.2.3github:Moeblack/dsh-message-editExact version not resolved