Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.3 · last checked Install verification details →
Showing badges for the 5 most recent dsh versions; older ones are hidden.
Data as of (UTC)
What it doesAI
Shows real-time multi-vendor account balances and quotas in the DeepSeek Harness Web GUI model selector.
- Displays live account balance per AI provider in composer
- Refreshes automatically when usage changes or model switches
- Uses official APIs (DeepSeek, OpenRouter, MiniMax, xAI, etc.)
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-model-balanceInstall method: npm · runtime verified (L5)
Trends
Four lines, four questions: total stars, stars gained this week, cumulative downloads, downloads this week. The GitHub pair comes from real-read sampling — a rotating daily shard, so one plugin is re-read roughly every 5–14 days, sparser than npm; the npm pair has a value on every snapshot day. The two cumulative panels are smoothed curves with no sample markers; the two weekly panels keep their raw bars and add a 4-week moving-average trend line that strips single-week noise down to the direction of travel.
11 samples (roughly every 7 days), 5 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-18 → 11-14 · 11 points
Bars = the delta between two samples 5–14 days apart (negative points down, faint bars contain reconstructed points); line = 4-week moving-average trend
09-28 → 11-14 · 10 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
08-19 → 11-14 · 73 points
Bars = the snapshot’s last-week rolling window (official npm + npmmirror combined); line = 4-week moving-average trend — the shape of weekly demand, not a user count
08-19 → 11-16 · 74 points
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.2-rc.3 current | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| 0.1.6 | ✓ | ✓ | ✓ | ✓ | · |
| 0.1.5 | · | · | · | · | ✓ |
| 0.1.4 | · | · | · | · | · |
| 0.1.2 | · | · | · | · | · |
| 0.1.1 | · | · | · | · | · |
0.1.6npm✓ 4 runtime-verified2026-11-15
dsh-model-balance
✓dsh 0.2.2-rc.3current2026-11-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: npm · dsh-model-balance@0.1.6
ID: dsh-model-balance@0.1.6@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-15 · expires: 2026-11-22
View checks & evidence
active in loader tree (206 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.2-rc.12026-11-06L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · dsh-model-balance@0.1.6
ID: dsh-model-balance@0.1.6@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-06 · expires: 2026-11-13
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-rc.52026-11-01L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · dsh-model-balance@0.1.6
ID: dsh-model-balance@0.1.6@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
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-rc.32026-10-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-model-balance@0.1.6
ID: dsh-model-balance@0.1.6@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
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.
0.1.5npm✓ 5 runtime-verified2026-10-20
dsh-model-balance
✓dsh 0.2.1-rc.22026-10-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-model-balance@0.1.5
ID: dsh-model-balance@0.1.5@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
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-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-model-balance@0.1.5
ID: dsh-model-balance@0.1.5@dsh0.2.1-alpha.4 · 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.22026-10-12L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-model-balance@0.1.5
ID: dsh-model-balance@0.1.5@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
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.0-rc.22026-10-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-model-balance@0.1.5
ID: dsh-model-balance@0.1.5@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
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.
✓prehistory2026-10-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-model-balance@0.1.5
ID: dsh-model-balance@0.1.5@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
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.
0.1.4npm✓ 6 runtime-verified2026-09-30
dsh-model-balance
✓dsh 0.1.7-rc.22026-09-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-model-balance@0.1.4
ID: dsh-model-balance@0.1.4@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
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.1.7-rc.12026-09-24L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · dsh-model-balance@0.1.4
ID: dsh-model-balance@0.1.4@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
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.1.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · dsh-model-balance@0.1.4
ID: dsh-model-balance@0.1.4@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
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.1.6-alpha.12026-09-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · dsh-model-balance@0.1.4
ID: dsh-model-balance@0.1.4@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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.1.5-rc.22026-09-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: npm · dsh-model-balance@0.1.4
ID: dsh-model-balance@0.1.4@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
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.
✓prehistory2026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-model-balance@0.1.4
ID: dsh-model-balance@0.1.4@dshunknown · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
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.
0.1.2npm✓ 3 runtime-verified2026-09-08
dsh-model-balance
✓dsh 0.1.3-alpha.22026-09-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: npm · dsh-model-balance@0.1.2
ID: dsh-model-balance@0.1.2@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
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.1.3-alpha.12026-09-06L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: npm · dsh-model-balance@0.1.2
ID: dsh-model-balance@0.1.2@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-06 · expires: 2026-09-13
View checks & evidence
active in loader tree (151 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.2-rc.12026-09-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: npm · dsh-model-balance@0.1.2
ID: dsh-model-balance@0.1.2@dsh0.1.2-rc.1 · profile: l5-web-smoke
Issued: 2026-09-04 · expires: 2026-12-03
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.
0.1.1npm2026-09-08
dsh-model-balance
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 dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/dsh-model-balance/?ref=badge)``[](https://www.dsh.so/artifact/dsh-model-balance/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-model-balance/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-model-balance/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-model-balance/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-model-balance/?ref=badge-install)`dsh.so is an independent community project, not affiliated with or endorsed by DeepSeek AI. Badges are maintained by dsh.so; embed links carry a ?ref= attribution parameter.
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 medium (authoritative when present) → overall medium.
v0.1.6dsh manifest0.1.6npm2026-11-170.1.6same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (2)
- criticalnewFunction · code-exec
lib/index.js:57const fn = new Function(`"use strict"; return (${resolved})`); - criticalnewFunction · code-exec
src/host/custom-providers.ts:180const fn = new Function(`"use strict"; return (${resolved})`)
show 2 audit findings
- mediumBalance route spends stored API keys for any caller and any configured provider ID, with no caller authorization check
src/host/index.ts:268The route handler checks only the HTTP method and that `provider` is non-empty; it never verifies a session, user or capability before resolving the stored credential from ctx.credentials and issuing the outbound request with it, and `refresh=1` bypasses the 60s cache entirely. Any client able to reach the DSH web server (including a cross-site GET fired by a page the user visits, which needs no CORS preflight) can make the harness call provider billing endpoints with the user's real keys, repeatedly, and can bind arbitrary attacker-chosen provider strings into the unbounded per-provider cache
- lowConfig-file expression strings are evaluated with new Function while the code claims this is a safe evaluation
src/host/custom-providers.ts:180Provider definitions from the bundled providers.json (not part of this harvest) and from ~/.dsh/model-balance-providers.json / $DSH_MODEL_BALANCE_CONFIG can supply `response: { expr: ... }`, whose text is compiled and run in the host process; the comment "no access to outer scope" is wrong because new Function still sees Node globals. Reachability requires write access to a local config file, and the preceding identifier substitution rewrites every ASCII identifier/dotted path to NaN, so only numeric/operator payloads (and at most unicode-escaped bare identifiers) survive — no practical RCE wa
Balance route performs credentialed provider queries for any caller and provider ID with no authorization check; new Function eval is config-file gated and payload-constrained.
Rule (2026-10-28): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); the static scan tier (vet primary, dsh backstop) applies only when there is none (not queued / audit failed / withdrawn). 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 the static scan tier.
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-08-15
• Stars: ★ 3 · 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).
Frequently asked questions
What is dsh-model-balance?
dsh-model-balance is a DeepSeek Harness (dsh) plugin listed on dsh.so — an independent community registry that indexes public source repositories and publishes automated security-scan and install-verification results for each entry.
Is dsh.so or this plugin page official?
dsh.so is an independent community registry and is not affiliated with, endorsed by, or sponsored by DeepSeek AI.
How do I install dsh-model-balance?
Run dsh plugin --profile web add dsh-model-balance in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4) plus web smoke testing (L5).
How does the security scan relate to a manual audit?
Both layers are automated, not a manual audit. The static scan is heuristic analysis of the repository source, so it can produce false positives and miss context. The model-driven dynamic security audit only covers plugins static-flagged at warn or above, never executes plugin code, and its conclusion is authoritative when there is one (it may raise or lower the static tier); exemptions stay manual. Neither layer is an endorsement: review the repository and the permissions it asks for before installing, together with the verification level and health signals.
How fresh is the data on this page?
The data on this page is as of 2026-11-17 (UTC) — the most recent valid timestamp among the registry refresh, install verification, security scan and dynamic audit. Build time is never used as a data date.
