What it may solve
Roll back to before any of your questions or edit the last one and resubmit, with the workspace files of the discarded turns restored.
Imported third-party catalog description; not a Registry verification conclusion.Roll back to before any of your questions or edit the last one and resubmit, with the workspace files of the discarded turns restored.
Author: dygin · UI Enhancements · Catalog snapshot: 2026-09-19Canonical semantic path
Roll back to before any of your questions or edit the last one and resubmit, with the workspace files of the discarded turns restored.
Imported third-party catalog description; not a Registry verification conclusion.4 stars · 1582 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, 15 commits, 0 forks, and 0 watches; latest commit 2026-09-01.
Conclusion: Resolved npm release 1.0.6, published 2026-09-01, license Apache-2.0.
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: may read environment variables, may create or modify files, 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-recover-context@1.0.6; SHA-256: f13b75e27d5b65ea330e04b42443a52604d8ad3dcd84d9b50d30c6201c22ca93.
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-recover-context. 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-recover-contextAnalyzed 1.0.6github:dygin/dsh-recover-contextExact version not resolved