Install verification: sandbox install failed (L4) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Audits DeepSeek Harness spend: shows per-turn and per-session RMB costs and re-measures savings after you adopt its suggestions.
- Per-turn and per-session RMB cost capsules drawn in native harness style
- Bills the context-compaction summary call separately, splitting manual vs auto compaction
- Suggestion engine names the spend drivers and re-measures the metric after adoption
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.
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); the npm pair from every snapshot.
6 samples (roughly every 7 days), 2 of them reconstructed (hollow dots); sampled points, not a daily series
09-24 → 10-31 · 6 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-01 → 10-31 · 5 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
The snapshot’s last-week rolling window (official npm + npmmirror combined)
Only 0 points (< 3): no chart yet
no data yet
Installation
dsh plugin --profile web add github:Pingze-github/dsh-cost-auditInstall method: GitHub · sandbox install failed (L4) · verified on dsh 0.2.1-rc.5
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
Based on 1 requirement(s) across 2 @deepseek-ai/dsh-* packages. raw ranges
^0.1.5-rc.1 ×2
✗ Running dsh 0.2.2-rc.1 is outside the declared range — the official install gate rejects it (incompatible-version).
To force-install, grant an exact-version exemption: dsh plugin allow-version dsh-cost-audit@0.1.0 0.2.2-rc.1 (the exemption lives in the local profile; this site does not assume one)
Deciding channel: no engines.dsh declared, so every dsh* peer is checked (workspace:^ | ~ | * counts as the running version).
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| plugin ＼ dsh | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| 0165fc | ✗ | ✗ | ✗ | ✗ | ✗ |
0165fcgithub10 failed2026-11-04
https://github.com/Pingze-github/dsh-cost-audit
✗dsh 0.2.1-rc.52026-10-31L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/Pingze-github/dsh-cost-audit (version unstated)
ID: dsh-cost-audit@0165fc@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
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.
✗dsh 0.2.1-rc.32026-10-26L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/Pingze-github/dsh-cost-audit (version unstated)
ID: dsh-cost-audit@0165fc@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
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.
✗dsh 0.2.1-rc.22026-10-18L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/Pingze-github/dsh-cost-audit (version unstated)
ID: dsh-cost-audit@0165fc@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/Pingze-github/dsh-cost-audit (version unstated)
ID: dsh-cost-audit@0165fc@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
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-11L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/Pingze-github/dsh-cost-audit (version unstated)
ID: dsh-cost-audit@0165fc@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/Pingze-github/dsh-cost-audit (version unstated)
ID: dsh-cost-audit@0165fc@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
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-29L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/Pingze-github/dsh-cost-audit (version unstated)
ID: dsh-cost-audit@0165fc@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.7-rc.22026-09-25L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/Pingze-github/dsh-cost-audit (version unstated)
ID: dsh-cost-audit@0165fc@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
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-23not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/Pingze-github/dsh-cost-audit (version unstated)
ID: dsh-cost-audit@0165fc@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
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.
✗dsh 0.1.6-alpha.22026-09-20L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/Pingze-github/dsh-cost-audit (version unstated)
ID: dsh-cost-audit@0165fc@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-10-05L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/Pingze-github/dsh-cost-audit (version unstated)
ID: dsh-cost-audit@0165fc@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-cost-audit@0165fc@dsh0.2.2-rc.1 (l3-fullscan)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
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-cost-audit/?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 low (authoritative when present) → overall low.
v0.1.1dsh manifest0.1.1git2026-11-050.1.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (7)
- warningnetIp · network
scripts/gui-probe.mjs:141const answer = await fetch(`http://127.0.0.1:${port}/json/list`); - warningnetIp · network
scripts/smoke.sh:29BASE="http://127.0.0.1:3080" - warningnetIp · network
scripts/smoke.sh:44grep -o 'http://127.0.0.1:3080/?token=[A-Za-z0-9_-]*' "$log" 2>/dev/null | tail -1 || true - warningnetIp · network
scripts/smoke.sh:46grep -o 'http://127.0.0.1:3080/?token=[A-Za-z0-9_-]*' /var/log/dsh-web.log 2>/dev/null | tail -1 || true - warningcurlDownload · network
scripts/smoke.sh:52curl -s -L -o /dev/null -c "$JAR" -b "$JAR" "$candidate" || continue - warningcurlDownload · network
scripts/smoke.sh:53code=$(curl -s -b "$JAR" -H 'Origin: http://127.0.0.1:3080' -o /dev/null -w '%{http_code}' "$BASE/_dsh/hotswap/state" || true) - warningcurlDownload · network
scripts/smoke.sh:61curl -s -L -o /dev/null -c "$JAR" -b "$JAR" "$TOKEN_URL"
show 4 audit findings
- lowAuthenticated /api routes fold and expose cost data for every session on the machine
index.jsThe .report and .fine routes enumerate every session on the host (up to REPORT_SESSION_CAP=400) and return their spend, model/effort names, spawn/command markers and sandbox/permission setting values; the .balance route also folds an arbitrary body.sessionId. Any client that reaches the route inherits machine-wide cost and session metadata rather than its own session. Mitigated by Connection's auth/Origin fence and by DSH being a single-user local harness, and the aggregate report is the plugin's documented purpose.
- low/api/dsh-cost-audit.fine re-folds every session log on each cache miss
index.jsThe fine cache is keyed by bucketMs|since|until|sessionId with only FINE_CACHE_ENTRIES=8 slots and a 60 s TTL; an authenticated client that varies those numbers forces repeated full-log folds over up to 400 sessions on the process that also serves the conversation. Impact is amplification/CPU on the host rather than data loss, and the author has already made the fold sequential and window-bounded.
- lowDeveloper script extracts the GUI auth token from /var/log/dsh-web.log into a /tmp cookie jar
scripts/smoke.sh:35The script greps the server's bearer token out of a log file and stores it as a cookie in ${TMPDIR:-/tmp}/dsh-cost-audit-smoke.cookies, which may be world-readable depending on umask. It is manual developer tooling against the operator's own localhost server and is excluded from the published 'files' list, so it is not reachable by plugin consumers.
- lowDeveloper probe spawns Chromium with --no-sandbox and evaluates argv-provided JS
scripts/gui-probe.mjsgui-probe.mjs runs chromium with --no-sandbox against a caller-supplied --url and evaluates arbitrary expressions from --report/--seed/--click over CDP, so a hostile page or a crafted argv can drive the probe's browser. It is a manual developer script, not part of the published package, and affects only the operator running it.
The host half is a bounded, read-only cost projection plus authenticated cost routes; every risky-looking construct sits in developer-only scripts, so residual risk is low.
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-24 · activity: Active
• Repo created: 2026-09-19
• Stars: ★ 0 · 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 @Pingze-github/dsh-cost-audit?
@Pingze-github/dsh-cost-audit 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 @Pingze-github/dsh-cost-audit?
Run dsh plugin --profile web add github:Pingze-github/dsh-cost-audit in a DeepSeek Harness (dsh) environment. The command is parsed from the plugin manifest and its install spec is verified (L3); runtime sandbox install testing may not have run yet.
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-05 (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.