What it may solve
Usage statistics panel: silent per-model token collection, activity heatmap, trend charts, cost estimation and daily-limit guard.
Imported third-party catalog description; not a Registry verification conclusion.Usage statistics panel: silent per-model token collection, activity heatmap, trend charts, cost estimation and daily-limit guard.
Author: hb-degithub · Usage & Billing · Catalog snapshot: 2026-09-19Canonical semantic path
Usage statistics panel: silent per-model token collection, activity heatmap, trend charts, cost estimation and daily-limit guard.
Imported third-party catalog description; not a Registry verification conclusion.1 stars · 671 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, 21 commits, 0 forks, and 0 watches; latest commit 2026-08-20.
Conclusion: Resolved npm release 0.1.0, published 2026-08-20, 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 4 code capabilities: may read environment variables, may create or modify files, may access the network, test, example, or support code contains additional capabilities outside the default runtime scope. No predefined elevated-risk condition was triggered; this is not proof of safety.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-usage-guard@0.1.0; SHA-256: b1414ba9521f80e3b9dc344b29e6b215f2d9525cf2b37202c596142e815a66b9.
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-usage-guard. 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-usage-guardAnalyzed 0.1.0github:hb-degithub/dsh-usage-guardExact version not resolved