dsh.so
EN
English中文
@HerTa-st/dsh-balance-card avatar

@HerTa-st/dsh-balance-card

DSH 余额与用量浮层卡片：点图片从左侧滑出 / 再点缩回 + 点击回弹动画 · 官方余额 + 本地会话 token 三段计价估算

PluginVisionVision / OCR
Verification
L4 · Install tested
Failed
Risk
LowRisk
Health
Active
Trust
Silver

Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →

What it does

DSH 余额与用量浮层卡片：点图片从左侧滑出 / 再点缩回 + 点击回弹动画 · 官方余额 + 本地会话 token 三段计价估算

Installation

dsh plugin --profile web add dsh-herta-balance-card
verified 0.1.0

Install method: npm · sandbox install ok, web smoke failed (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

Declared DSH compatibilityfrom package.json · peerDependencies
author declared no dsh version requirement

○ The author declares no dsh version requirement — install is not blocked by version.

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)
At-a-glance → evidence in the cards below
plugin ＼ dshdsh 0.2.1-rc.2
current
0.1.0✗
v0.1.0·
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
0.1.0npm1 failed2026-10-21

dsh-herta-balance-card

✗dsh 0.2.1-rc.2current2026-10-21L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-rc.2
  • • Plugin artifact: npm · dsh-herta-balance-card@0.1.0
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Passed
L5 runtime
Failed
Sandbox install failed
L5 · failed

ID: dsh-balance-card-2@0.1.0@dsh0.2.1-rc.2 · profile: l3-fullscan

Issued: 2026-10-21 · expires: 2026-10-28

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-21
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-21
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19
spec dsh-herta-balance-card · channel npm package · outcome ran · exit 0
check took: 3.4s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19
spec dsh-herta-balance-card · channel npm package · outcome ran · exit 0
check took: 3.4s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19
spec dsh-herta-balance-card · channel npm package · outcome ran · exit 0
check took: 3.4s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19
spec dsh-herta-balance-card · install mode reused L4 scratch
check took: 0ms
Web boot ready✕ Failed
plugin tree failed to load
HTTP endpoint served✕ Failed

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

v0.1.0github2026-10-18

https://github.com/HerTa-st/dsh-balance-card

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

Author badges

Embed the official badges in your README to showcase security & install-test status:

dsh.so risk
`[![dsh.so risk](https://www.dsh.so/badge/dsh-balance-card-2.svg)](https://www.dsh.so/artifact/dsh-balance-card-2/)`

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.

dsh-balance-card-2Automated review · daily

Static low, dynamic low — stricter wins → overall low.

static low→dynamic low→overall low
0 critical·0 high
lowoverall · low
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
Version binding
plugin versionv0.1.0dsh manifest
scanned version0.1.0npm2026-10-21
current version0.1.0same version
vet verdictclean · npm

Vet is an AST static scan (npm artifact or git source).

show static findings (1)
  • warningnetIp · networklib/index.js:376

    const url = new URL(req.url ?? DATA_ROUTE, "http://127.0.0.1");

2dynamic auditmodel reads redacted source context · never executes plugin code
highest gradelow
merged intooverall low
audited at2026-10-19
findings0 critical·0 high0 medium / 3 low hidden
show 3 audit findings
  • lowRuntime entry lib/index.js and lib/client.js are absent from the audited sourcepackage.json:7

    The code that actually holds the API key reference, scans session logs and calls the configurable balanceUrl was not reviewable, so its behavior (validation, request target, retention of key material) cannot be confirmed here.

  • lowDev scripts load Node modules from attacker-influenced env vars and eval in a CDP pagescripts/measure-open.mjs:18

    Running this helper with a hostile DSH_WS loads and executes an arbitrary module; related scripts also require(process.env.DSH_SHARP) and drive a remote-debugging browser. Both require the developer to run the script with a lab URL token, and scripts/ is excluded from package.json "files", so registry users never receive it.

  • lowDeveloper scripts hardcode local profile paths and the machine user namescripts/bench-usage.mjs:12

    Publishes a local username and directory layout in the repository; no runtime impact since the scripts are not shipped.

All reachable risky constructs live in dev-only scripts/ excluded from the published package; lib/index.js and lib/client.js were not in the audited set, a residual gap.

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-19 · activity: Active

• Repo created: 2026-10-18

• Stars: ★ 0 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/HerTa-st/dsh-balance-card

Was this page helpful?