The original repository has been deleted or made private. This page is an archival snapshot from indexing time; the install command may no longer work.
Install verification: Ecosystem app: not installed via dsh plugin add, so the L1-L5 plugin install-verification ladder does not apply; the security scan still runs.Install verification details →
Data as of (UTC)
What it doesAI
Session-level token usage and cost panel for DSH that parses local session archives into dashboards, trends and cost ledgers.
- Three-surface Apple-style UI: sidebar dashboard, composer status bar, dock
- Four-state pricing (official/community/shadow/unpriced), never silently shows ¥0
- Local-first, read-only, no telemetry; agent usage query tool with since/until/group by
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.
4 samples (roughly every 1 days), 4 of them reconstructed (hollow dots); sampled points, not a daily series
09-28 → 10-04 · 4 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
Only 2 points (< 3): no chart yet
10-03 → 10-04 · 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
The snapshot’s last-week rolling window (official npm + npmmirror combined)
Only 0 points (< 3): no chart yet
no data yet
Installation
Ecosystem apps are not installable via dsh plugin add: desktop / web shells install or deploy through their own release channel (GitHub Releases or the project site).
The level reads L5 · Ecosystem plugin / L5 · Ecosystem app per the three-way classification (the L1-L5 ladder does not rate them); the security scan still runs.
Verification & Compatibility◼ Ecosystem app
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
| plugin ＼ dsh | dsh 0.2.0-rc.1 | dsh 0.1.7-rc.2 | prehistory |
|---|---|---|---|
| e50ae8 | ◼ | ✗ | ◼ |
e50ae8github◼ 2 ecosystem app1 failed2026-10-05
https://github.com/qikairo7/dsh-usage-panel
◼dsh 0.2.0-rc.12026-09-30Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/qikairo7/dsh-usage-panel (version unstated)
ID: dsh-usage-panel-4@e50ae8@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
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.
✗dsh 0.1.7-rc.22026-09-25Ecosystem app · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/qikairo7/dsh-usage-panel (version unstated)
ID: dsh-usage-panel-4@e50ae8@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
◼prehistory2026-10-05Ecosystem app
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/qikairo7/dsh-usage-panel (version unstated)
ID: dsh-usage-panel-4@e50ae8@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
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 dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/dsh-usage-panel-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.
v0.1.0dsh manifest0.1.0git2026-10-070.1.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (1)
- criticalsecretSk · secrets
scripts/sanitize-fixtures.mjs:25'main-with-usage.v4.zstd': 'D:/dsh-data/sessions/--C-Users-Administrator-AppData-Local-Temp-sk-probe-speckit-dsh-probe--/session-286aac50-29
show 3 audit findings
- mediumSame-origin fence fails open when Sec-Fetch-Site is absent on the unauthenticated usage API
src/lib/rpc-envelope.ts:70Every /usage-panel/api/* route is POST-only but otherwise unauthenticated, and the only gate treats a missing Sec-Fetch-Site header as trusted. Any local process can read aggregated session usage (session ids, models, providers, token/cost totals, ledger channels) and can trigger rescans via the 'refresh' endpoint. The same fail-open logic removes the browser-side protection if the host web server does not validate the Host header, since a DNS-rebinding page is seen by the browser as same-origin. The loopback binding and the fact that a same-user local process can already read $DSH_HOME cap th
- lowRequest body is buffered without any size limit
src/lib/rpc-envelope.ts:76readBody concatenates the whole stream into a string before any parsing, so a single large POST (from any local process, or from a page that passes the fence) can inflate host memory. The payload is only JSON.parse'd afterwards, and the parsed object is never size-checked either.
- lowDev sanitizer script hardcodes the author's absolute local paths and user names
scripts/sanitize-fixtures.mjs:25The script documents the developer's machine layout (D:/dsh-data, 'Administrator', workspace names). It is not part of the runtime: only lib/, src/, data/ and cordis.patch.yml ship in the npm tarball, so this is not reachable when installed via `dsh plugin add` from the registry. A git-based install does carry it, and running it would read and overwrite fixtures under tests/ with data copied from those absolute paths — read-only for the panel itself.
Static 'critical' not reproducible: the audited code is a read-only usage API behind a same-origin fence; only hardening gaps (fail-open fence, unbounded body, dev-script path leaks) were found.
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-25 · activity: Stable
• Repo created: 2026-09-24
• 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 @qikairo7/dsh-usage-panel?
@qikairo7/dsh-usage-panel is an ecosystem app listed on dsh.so, not a DSH plugin package: it cannot be installed with dsh plugin add and ships through the project's own release channel.
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 @qikairo7/dsh-usage-panel?
This is an ecosystem app, not a plugin installable via dsh plugin add: desktop / web shells install or deploy through their own release channel. The security scan still runs, but the L1-L5 plugin install ladder does not rate it.
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-16 (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.