Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
Aggregates historical token usage across all local DSH sessions, deduped by message.id, with breakdowns by day, model, provider, and project.
- Global totals across sessions, workspaces, and DSH homes
- Dedupes by message.id, avoiding ~3x inflation from fork/resume copies
- Read-only multi-dimensional breakdown: day, model, provider, project, session
Capability tags are AI-inferred or rule-extracted from the README (see badge) — vocabulary-limited, not install-verified. AI = inferred; README = literal keyword from the readme.
Installation
dsh plugin --profile web add @liuguangzhe/dsh-token-usage@0.4.1security scan passed · npm package v0.4.1
Install method: npm · runtime verified (L5)
Verification & Compatibility
Grouped by plugin version: each card lists the dsh versions actually tested against that artifact version and their install verdicts (L5 wins). Untested combinations are omitted — absence means untested, never assumed compatible. L1–L3 are a plugin-level static archive (independent of the dsh version — the same verdict on every dsh row): they sit in each row's level grid next to L4/L5, marked "static", while their evidence is stored once per plugin inside that row's "checks & evidence" instead of being duplicated per version.
External credentials (plugin-level): none detected
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.1-rc.2 current | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 | dsh 0.2.0-rc.1 |
|---|---|---|---|---|---|
| 0.4.1 | · | · | · | · | · |
| 0.1.1 | ✓ | ✗ | ✓ | ✗ | ✓ |
| 0.1.0 | · | · | · | · | · |
0.4.1npm2026-10-23
@liuguangzhe/dsh-token-usage
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.1.1npm✓ 3 runtime-verified7 failed2026-10-19
@liuguangzhe/dsh-token-usage
✓dsh 0.2.1-rc.2current2026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · @liuguangzhe/dsh-token-usage@0.1.1
ID: dsh-token-usage-19@0.1.1@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-alpha.42026-10-16L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · @liuguangzhe/dsh-token-usage@0.1.1
ID: dsh-token-usage-19@0.1.1@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.1-alpha.22026-10-10L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · @liuguangzhe/dsh-token-usage@0.1.1
ID: dsh-token-usage-19@0.1.1@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
View checks & evidence
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.0-rc.22026-10-08L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · @liuguangzhe/dsh-token-usage@0.1.1
ID: dsh-token-usage-19@0.1.1@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.0-rc.12026-09-29L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · @liuguangzhe/dsh-token-usage@0.1.1
ID: dsh-token-usage-19@0.1.1@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.7-rc.22026-09-25L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · @liuguangzhe/dsh-token-usage@0.1.1
ID: dsh-token-usage-19@0.1.1@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.7-rc.12026-09-24L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · @liuguangzhe/dsh-token-usage@0.1.1
ID: dsh-token-usage-19@0.1.1@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
View checks & evidence
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.7-alpha.22026-09-23L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: npm · @liuguangzhe/dsh-token-usage@0.1.1
ID: dsh-token-usage-19@0.1.1@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.6-alpha.22026-09-20L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · @liuguangzhe/dsh-token-usage@0.1.1
ID: dsh-token-usage-19@0.1.1@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-10-05L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · @liuguangzhe/dsh-token-usage@0.1.1
ID: dsh-token-usage-19@0.1.1@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-token-usage-19@0.4.1@dsh0.2.1-rc.2 (l3-fullscan)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.1.0npm2026-09-18
@liuguangzhe/dsh-token-usage
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
Only the latest 3 published versions are shown; source-snapshot (commit hash) groups, unstated groups and older versions are omitted — the full archive stays in the data layer (snapshot/unstated groups appear only when a plugin has no published version).
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-token-usage-19/)``[](https://www.dsh.so/artifact/dsh-token-usage-19/)``[](https://www.dsh.so/artifact/dsh-token-usage-19/)`Security Report
Two automated layers, neither a manual review: a static scan (per-plugin rule checks) and a model-driven dynamic security audit that covers only the subset static-flagged at warn or above and never executes plugin code.
Static low; dynamic no conclusion (static stands) → overall low.
v0.4.1dsh manifest0.4.1npm2026-10-250.4.1same versionclean · npmVet is an AST static scan (npm artifact or git source).
not in the dynamic queue (the queue only covers plugins whose static tier is medium or above — medium/high/critical; since 2026-10-24 entries rated low are not audited even when dsh-only rules logged warnings) — this does not mean the dynamic audit found it safe.
Rule (2026-10-24): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); without one, the static/vet fused tier applies. The audit never writes the exemption list (exemptions are manual only); a wrong conclusion is withdrawn by human review and the tier falls back to static/vet.
Disclaimer: the static scan and the dynamic security audit are both automated analysis, not a security guarantee. Always review what you install.
Activity
Last commit 2026-10-22 · activity: Active
• Repo created: 2026-09-11
• Stars: ★ 1 · Forks: 1
• Health: Active — committed within last 30 days
Source
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
