Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
A draggable floating window that shows your DeepSeek Harness token usage as a GitHub-style contribution heatmap.
- GitHub-style contribution heatmap of token usage: 30-day view plus a hover-expanded yearly panel
- Shows daily totals with input / cache / output breakdown, active days, streaks and best day
- Draggable with remembered position, double-click to collapse; reads local session logs offline
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 github:cccchensy/dsh-token-heatmapInstall method: GitHub · 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 |
|---|---|---|---|
| a936be | ✓ | ✓ | ✓ |
a936begithub✓ 3 runtime-verified2026-10-19
https://github.com/cccchensy/dsh-token-heatmap
✓dsh 0.2.1-rc.2current2026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/cccchensy/dsh-token-heatmap (version unstated)
ID: dsh-token-heatmap-3@a936be@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
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 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/cccchensy/dsh-token-heatmap (version unstated)
ID: dsh-token-heatmap-3@a936be@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
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.22026-10-14L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/cccchensy/dsh-token-heatmap (version unstated)
ID: dsh-token-heatmap-3@a936be@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-14 · expires: 2026-10-21
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-token-heatmap-3/)``[](https://www.dsh.so/artifact/dsh-token-heatmap-3/)`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 low — stricter wins → overall low.
v0.1.0dsh manifest0.1.0git2026-10-210.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (6)
- criticalnewFunction · code-exec
verify-client.mjs:198new Function(source)(); - criticalnewFunction · code-exec
verify-client.mjs:525const build = new Function('window', 'document', ` - criticalnewFunction · code-exec
verify-client.mjs:585const formatting = new Function(`${lifted}\nreturn { formatTokens, formatExact, formatDay, formatAge };`); - warningchildProcess · code-exec
verify.mjs:305return spawnSync(process.execPath, [fileURLToPath(import.meta.url)], { - warningfsWrite · files
verify.mjs:207await fs.writeFile(path.join(root, dir, 'session.v4.jsonl'), [header, ...lines].join('\n') + '\n'); - warningfsWrite · files
verify.mjs:273await fs.writeFile(path.join(root, dir, 'session.v4.jsonl'), [header, ...lines].join('\n') + '\n');
show 1 audit findings
- lowDev-only verification script evaluates the bundle via new Function (not shipped, not loaded at runtime)
verify-client.mjs:198This harness reads lib/client.js and evaluates its body in the Node test process. That is arbitrary code execution in the developer's shell, but only over a file in the same repo, and the very same code is executed by the Harness page itself. package.json `files` excludes verify-client.mjs from the published artifact and no runtime path loads it, so there is no reachable exposure in the shipped plugin.
Static 'critical' hits are eval/child-process use inside dev-only verification scripts excluded from the published package; the shipped browser bundle has no real risk, so the warn is refuted.
Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.
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-13 · activity: Active
• Repo created: 2026-10-01
• Stars: ★ 4 · Forks: 0
• 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).