What it may solve
Minimal ↑/↓ input history for the DSH web composer: press ↑/↓ to walk back through sent messages. Nothing else.
Imported third-party catalog description; not a Registry verification conclusion.Minimal ↑/↓ input history for the DSH web composer: press ↑/↓ to walk back through sent messages. Nothing else.
Author: NormanFxxkingRockwell · UI Enhancements · Catalog snapshot: 2026-09-19Canonical semantic path
Minimal ↑/↓ input history for the DSH web composer: press ↑/↓ to walk back through sent messages. Nothing else.
Imported third-party catalog description; not a Registry verification conclusion.NormanFxxkingRockwell/dsh-keyboard-history
1 stars · 307 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: 2 stars, 16 commits, 1 forks, and 0 watches; latest commit 2026-08-19.
Conclusion: Resolved npm release 0.1.2, published 2026-08-19, 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 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-keyboard-history@0.1.2; SHA-256: 411d1b7cac537fab91960b7e911c7dd8a5513576c6c00e78bddd94e7946ece41.
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-keyboard-history. 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-keyboard-historyAnalyzed 0.1.2github:NormanFxxkingRockwell/dsh-keyboard-historyExact version not resolved