What it may solve
DeepSeek-styled cross-session token usage, request count, and tiered cost analytics dashboard.
Imported third-party catalog description; not a Registry verification conclusion.dsh-token-usage-stats
Automated evidence availableDeepSeek-styled cross-session token usage, request count, and tiered cost analytics dashboard.
Author: jkStars · Usage & Billing · Catalog snapshot: 2026-09-19Canonical semantic path
Usage, Cost & Resource GovernanceConsumption Metering & ObservabilityRuntime Telemetry & Performance Observability
One primary path; alternate capabilities remain separate.Sources and public signals
2 stars · 28161 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19What can currently be confirmed
Active analysis coverage 1/5. Historical chains are retained but do not count toward current coverage.
Source structure
Source structure has not been analyzed.
Repository health
Repository metadata has not been analyzed.
npm release
npm release metadata has not been analyzed.
DSH compatibility
Conclusion: Compatibility verification passed. Installation, profile loading, and sustained startup all completed. Test environment: DSH 0.1.6-alpha.2, web profile.
Dependency audit
Conclusion: This bounded audit reported 0 known vulnerabilities. It covers only the locked versions and audit source; zero reports is not proof of safety.
Functional verification
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Static risk scan
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.
Package integrity
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-token-usage-stats@0.3.13; SHA-256: 8b2454a7fa5b42f14bde92721ff4c54a39aa3b6552d4f3ca6b29dd403a6682fe.
Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.
Continue with the latest plugin manager
Describe your task in a DSH conversation and mention dsh-token-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.
Sources available for local inspection
- npm package
dsh-token-usage-statsAnalyzed 0.3.13 - GitHub source
github:jkStars/dsh-token-usage-statsExact version not resolved