Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
DeepSeek Harness plugin showing multi-platform API balances, session usage estimates and sub-agent consumption inside the Web GUI.
- Persistent balance capsule under the input box shows each platform's API balance
- Shows estimated session consumption with one-click sub-agent detail
- One responsive web plugin shared by phone, tablet and desktop browsers
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 dsh-api-dashboardInstall 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 |
|---|---|---|---|
| 1.7.0 | ✓ | ✓ | ✓ |
| v1.7.0 | · | · | ◐ |
1.7.0npm✓ 3 runtime-verified2026-10-18
dsh-api-dashboard
✓dsh 0.2.1-rc.2current2026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-api-dashboard@1.7.0
ID: dsh-api-dashboard@1.7.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
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-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-api-dashboard@1.7.0
ID: dsh-api-dashboard@1.7.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-15 · expires: 2026-10-22
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-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-api-dashboard@1.7.0
ID: dsh-api-dashboard@1.7.0@dsh0.2.1-alpha.2 · profile: l3-fullscan
Issued: 2026-10-15 · expires: 2026-10-22
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.
v1.7.0github◐ 1 testing2026-10-14
https://github.com/133563825as-ai/dsh-api-dashboard
◐dsh 0.2.1-alpha.22026-10-14L4 · testing (install passed, runtime untested)
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/133563825as-ai/dsh-api-dashboard#v1.7.0
ID: dsh-api-dashboard@v1.7.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-14 · expires: 2026-10-21
View checks & evidence
This level was not executed in this scan.
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-api-dashboard/)``[](https://www.dsh.so/artifact/dsh-api-dashboard/)`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.
v1.7.0dsh manifest1.7.0npm2026-10-211.7.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningshellExec · shell
src/index.js:366execFileSync('tar', ['xzf', tgzPath, '-C', extractDir, '--strip-components=1'], { timeout: 20000 }) - warningshellExec · shell
src/index.js:385execFileSync(process.execPath, ['--check', join(extractDir, rel)], { timeout: 10000, stdio: 'ignore' }) - warningshellExec · shell
src/index.js:395execFileSync('tar', ['czf', `${dir}.preupdate-${stamp}.tar.gz`, '-C', dirname(dir), basename(dir)], { timeout: 20000 }) - warningnetIp · network
src/index.js:1819const ALERT_BRIDGE_URL = 'http://127.0.0.1:3090/app/notify' - warningnetIp · network
src/index.js:1822const ALERT_BRIDGE_TOAST = 'http://127.0.0.1:3090/app/toast' - warningnetIp · network
src/index.js:1825const ALERT_BRIDGE_PROBE = 'http://127.0.0.1:3090/app/version'
show 2 audit findings
- lowSelf-update downloads a GitHub tarball and overwrites the running plugin source
src/index.js:430Compromise of the REPO_OWNER/REPO_NAME GitHub repository or of a published release would result in arbitrary code being installed and executed with host privileges on every user who clicks update. Mitigated by an explicit user confirmation with a sha256 confirmationToken, a pinned ref/version, manifest name+version+peer checks, extraction-time verification and node --check, plus backup/rollback; args are passed to execFileSync without a shell, so no shell injection is reachable.
- lowUpdate also wipes an auto-detected ~/dsha-api-dashboard directory that only needs a package.json
src/index.js:390A user who happens to keep an unrelated project (e.g. an extracted tarball, no .git) at ~/dsha-api-dashboard would have its contents deleted and replaced during a one-click update. Data loss only, path is fixed and not attacker-influenced, and a pre-update tar backup is written next to the directory.
Static warnings are explained by the plugin's legitimate design; no critical, high or medium risk found, only self-update supply-chain and legacy-directory sync concerns (low).
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-10 · activity: Active
• Repo created: 2026-08-25
• Stars: ★ 17 · 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).
