Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.5 · 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
Browse the curated dpharness.com plugin catalog inside dsh and install chosen plugins with one click.
- Browses the dpharness.com curated plugin catalog inside dsh
- One-click install for selected plugins
- Curated picks favor Chinese localization and trusted sources
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), 3 of them reconstructed (hollow dots); sampled points, not a daily series
09-18 → 10-26 · 6 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
09-23 → 10-26 · 5 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-21 → 10-30 · 38 points
The snapshot’s last-week rolling window (official npm + npmmirror combined)
09-21 → 10-30 · 38 points
Installation
dsh plugin --profile web add dsh-dpharnessInstall method: npm · runtime verified (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
Based on 1 requirement(s) across 1 @deepseek-ai/dsh-* packages. raw ranges
>=0.1.0-rc.5 ×1
✓ Running dsh 0.2.1-rc.5 is within the declared range — install is not blocked by version.
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 current | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 |
|---|---|---|---|---|---|
| 0.7.0 | ✓ | · | · | · | · |
| 0.6.10 | · | · | · | · | · |
| 0.6.9 | · | ✓ | · | · | · |
| 0.6.8 | · | · | · | · | · |
| 0.6.6 | · | · | · | · | · |
0.7.0npm✓ 1 runtime-verified2026-11-01
dsh-dpharness
✓dsh 0.2.1-rc.5current2026-11-01L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · dsh-dpharness@0.7.0
ID: dsh-dpharness@0.7.0@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.
0.6.10npm2026-10-28
dsh-dpharness
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.6.9npm✓ 1 runtime-verified2026-10-27
dsh-dpharness
✓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-dpharness@0.6.9
ID: dsh-dpharness@0.6.9@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.6.8npm2026-10-24
dsh-dpharness
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.6.6npm2026-10-22
dsh-dpharness
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-dpharness/?ref=badge)``[](https://www.dsh.so/artifact/dsh-dpharness/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-dpharness/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-dpharness/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-dpharness/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-dpharness/?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 high (authoritative when present) → overall high.
v0.7.0dsh manifest0.7.0npm2026-11-010.7.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (7)
- warningchildProcess · code-exec
lib/index.js:564const child = spawn(invocation.file, [...invocation.args, "plugin", "--profile", PROFILE, installJob.verb, target], { - warningnetIp · network
lib/index.js:1044const url = new URL(req.url || "/", "http://127.0.0.1"); - warningnetIp · network
lib/index.js:1065return new URL(req.url || "/", "http://127.0.0.1").searchParams; - warningfsWrite · files
lib/index.js:1459fs.writeFileSync(file, fresh, "utf8"); - warningfsWrite · files
lib/index.js:2041fs.writeFileSync(file, JSON.stringify({ at: now }), "utf8"); - warningfsWrite · files
lib/index.js:2572fs.writeFileSync(file, JSON.stringify({ on, at: Date.now() }), "utf8"); - warningfsWrite · files
lib/usage.js:204fs.writeFileSync(tmp, JSON.stringify(cache));
show 4 audit findings
- highLocal admin routes lack Origin/Host/CSRF checks, enabling drive-by install/uninstall/toggle
lib/index.jsAny web page or DNS-rebinding origin that can reach the dsh web port can issue simple POSTs (JSON body with text/plain) to /api/dpharness/install and /api/dpharness/toggle. That allows attacker-chosen package installation/removal and plugin disabling; a malicious npm package can execute code. Responses may be blocked by CORS, but side effects still occur, and DNS rebinding can also read responses.
- mediumCatalog fields are interpolated into copyable shell commands without validation
lib/index.jspkgName/fullName come from the remote catalog response and are embedded verbatim into commands shown to users. A compromised or malicious catalog entry could inject shell metacharacters/newlines into the copied command, leading to command execution under the user's account when they paste it into a terminal.
- mediumInstall subprocess strips the host safe-delete shim from PATH/NODE_OPTIONS
lib/index.jsEvery install/remove child process runs without the host's deletion guard. Combined with the unrestricted install target route, a malicious or compromised package's lifecycle scripts can perform deletions that the shim was intended to block, weakening a defense-in-depth control.
- mediumMeta route exposes cached search keywords
lib/index.js/api/dpharness/meta returns the cache key list, which contains the q= value from recent searches. This leaks user search terms to any local HTTP caller and, with DNS rebinding or an exposed dsh web port, to a remote attacker, contradicting the stated privacy contract that search keywords are not relayed.
Host routes expose unauthenticated local admin actions (install/uninstall/toggle) without Origin/Host checks; catalog fields also build shell commands and the host security shim is stripped for installs.
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-30 · activity: Active
• Repo created: 2026-09-17
• Stars: ★ 1 · 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-dpharness?
dsh-dpharness 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-dpharness?
Run dsh plugin --profile web add dsh-dpharness 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-01 (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.