What it may solve
Lightweight usage analytics for DeepSeek Harness — token trends, activity heatmaps, model breakdowns, and exports.
Imported third-party catalog description; not a Registry verification conclusion.Lightweight usage analytics for DeepSeek Harness — token trends, activity heatmaps, model breakdowns, and exports.
Author: lanlandeli · Usage & Billing · Catalog snapshot: 2026-09-19Canonical semantic path
Lightweight usage analytics for DeepSeek Harness — token trends, activity heatmaps, model breakdowns, and exports.
Imported third-party catalog description; not a Registry verification conclusion.— stars · 4263 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: 12 stars, 40 commits, 4 forks, and 0 watches; latest commit 2026-08-17.
Conclusion: Resolved npm release 0.1.16, published 2026-08-17, 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 2 code capabilities: 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-usage-stats@0.1.16; SHA-256: 9a7bb2f4bade5d417bd85a7d3ea1b5c6ff04e63f0015416763a15989abd90d6b.
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-stats. 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-statsAnalyzed 0.1.16github:lanlandeli/dsh-usage-statsExact version not resolved