Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.3 · 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
Bridges local Claude Code CLI into dsh web sessions, rendering Claude streams natively and handling permissions and questions.
- Engine selector per session: DSH or Claude Code
- Native rendering of Claude stream as dsh events
- Bridges Claude permissions to dsh approval UI
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 github:GeekRicardo/claude-in-dsh#v1.3.0Install method: GitHub · runtime verified (L5) · verified on dsh 0.2.2-rc.3
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.
current (registry 2026-11-12) · 9 samples (roughly every 7 days), 5 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-18 → 11-05 · 9 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
09-28 → 11-05 · 8 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
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.2-rc.3 | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| v1.3.0 | ✓ | ✓ | ✓ | ✓ | ✓ |
v1.3.0github✓ 18 runtime-verified2026-11-17
https://github.com/GeekRicardo/claude-in-dsh
✓dsh 0.2.2-rc.32026-11-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/GeekRicardo/claude-in-dsh#v1.3.0
ID: claude-in-dsh@v1.3.0@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-17 · expires: 2026-11-24
View checks & evidence
active in loader tree (206 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.2-rc.12026-11-06L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/GeekRicardo/claude-in-dsh#v1.3.0
ID: claude-in-dsh@v1.3.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-06 · expires: 2026-11-13
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.
✓dsh 0.2.1-rc.52026-11-01L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/GeekRicardo/claude-in-dsh#v1.3.0
ID: claude-in-dsh@v1.3.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.
✓dsh 0.2.1-rc.32026-10-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/GeekRicardo/claude-in-dsh#v1.3.0
ID: claude-in-dsh@v1.3.0@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.
✓dsh 0.2.1-rc.22026-10-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/GeekRicardo/claude-in-dsh#v1.3.0
ID: claude-in-dsh@v1.3.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
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.
✓dsh 0.2.1-alpha.42026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/GeekRicardo/claude-in-dsh#v1.3.0
ID: claude-in-dsh@v1.3.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
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.
✓dsh 0.2.1-alpha.22026-10-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/GeekRicardo/claude-in-dsh#v1.3.0
ID: claude-in-dsh@v1.3.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
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.
✓dsh 0.2.0-rc.22026-10-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/GeekRicardo/claude-in-dsh#v1.3.0
ID: claude-in-dsh@v1.3.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
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.
✓dsh 0.2.0-rc.12026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/GeekRicardo/claude-in-dsh#v1.3.0
ID: claude-in-dsh@v1.3.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
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.
✓dsh 0.1.7-rc.22026-09-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/GeekRicardo/claude-in-dsh#v1.3.0
ID: claude-in-dsh@v1.3.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-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.
✓dsh 0.1.7-alpha.22026-09-23L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/GeekRicardo/claude-in-dsh#v1.3.0
ID: claude-in-dsh@v1.3.0@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
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.
✓dsh 0.1.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/GeekRicardo/claude-in-dsh#v1.3.0
ID: claude-in-dsh@v1.3.0@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
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.
✓dsh 0.1.6-alpha.12026-09-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/GeekRicardo/claude-in-dsh#v1.3.0
ID: claude-in-dsh@v1.3.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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.
✓dsh 0.1.5-rc.22026-09-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/GeekRicardo/claude-in-dsh#v1.3.0
ID: claude-in-dsh@v1.3.0@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
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.
✓dsh 0.1.3-alpha.22026-09-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/GeekRicardo/claude-in-dsh#v1.3.0
ID: claude-in-dsh@v1.3.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
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.
✓dsh 0.1.3-alpha.12026-09-07L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/GeekRicardo/claude-in-dsh#v1.3.0
ID: claude-in-dsh@v1.3.0@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
active in loader tree (151 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.2-rc.12026-09-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/GeekRicardo/claude-in-dsh#v1.3.0
ID: claude-in-dsh@v1.3.0@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
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.
✓prehistory2026-10-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/GeekRicardo/claude-in-dsh#v1.3.0
ID: claude-in-dsh@v1.3.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
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.
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/claude-in-dsh/?ref=badge)``[](https://www.dsh.so/artifact/claude-in-dsh/?ref=badge-install)``[](https://www.dsh.so/artifact/claude-in-dsh/?ref=badge-install)``[](https://www.dsh.so/artifact/claude-in-dsh/?ref=badge-install)``[](https://www.dsh.so/artifact/claude-in-dsh/?ref=badge-install)``[](https://www.dsh.so/artifact/claude-in-dsh/?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 high; dynamic medium (authoritative when present) → overall medium.
v1.3.0dsh manifestv1.3.0git2026-11-19v1.3.0same versionsuspicious · gitVet is an AST static scan (npm artifact or git source).
show static findings (12)
- criticalnewFunction · code-exec
src/client-rig.mjs:130const closure = new Function('React', 'console', 'styles', 'host', 'harness', `return (async () => {\n${source}\n})()`) - warningfsWrite · files
install.sh:75if (changed) { fs.writeFileSync(p, JSON.stringify(json, null, 2) + "\n"); console.log("updated"); } - warningchildProcess · code-exec
lib/broker.mjs:32const child = spawn(argv[0], argv.slice(1), { stdio: ['pipe', 'pipe', 'pipe'] }) - warningfsWrite · files
lib/broker.mjs:26const out = fs.createWriteStream(dir + '/out.log', { flags: 'a' }) - warningfsWrite · files
lib/broker.mjs:37fs.writeFileSync(dir + '/meta.json', JSON.stringify({ ...meta, ...patch })) - warningfsWrite · files
lib/broker.mjs:56try { fs.writeFileSync(dir + '/exit.json', JSON.stringify({ code: code, signal: signal, at: Date.now() })) } catch (error) { /* best effort - warningchildProcess · code-exec
lib/index.js:286const proc = silenceStdin(subprocess.spawn({ - warningchildProcess · code-exec
lib/index.js:740const proc = silenceStdin(subprocess.spawn({ - warningchildProcess · code-exec
lib/index.js:923const writer = silenceStdin(subprocess.spawn({ - warningnetIp · network
scripts/safe-restart.sh:33curl -s -m 5 -X POST http://127.0.0.1:8090/claude-in-dsh/rpc \ - warningnetIp · network
scripts/safe-restart.sh:69if curl -sf -m 3 http://127.0.0.1:8090/ -o /dev/null; then say "dsh-web 已就绪"; exit 0; fi - warningcurlDownload · network
scripts/safe-restart.sh:69if curl -sf -m 3 http://127.0.0.1:8090/ -o /dev/null; then say "dsh-web 已就绪"; exit 0; fi
show 4 audit findings
- mediumClaude OAuth access token is read from disk and passed as a curl command-line argument
lib/index.jsloadUsage() reads the user's Claude Code OAuth token from ~/.claude/.credentials.json and puts it into the argv of `/usr/bin/env curl`, which on default Linux configurations is readable by any local user via /proc/<pid>/cmdline while the request is in flight. The destination is the legitimate api.anthropic.com, so this is credential exposure to co-tenants, not remote exfiltration.
- mediumPredictable, unowned /tmp/ccmode is created with mkdir -p and written via cat > without ownership or symlink checks
lib/index.jsThe directory name is fixed (/tmp/ccmode, plus per-session subdirectories derived from sanitized session ids). A local attacker who creates that directory first can own it and plant symlinks (broker.mjs, session-*/out.log, session-*/meta.json) so the plugin's `cat >`/`touch`/`printf >` write through them as the victim user, and can also pre-seed meta.json/out.log so the attach path feeds forged Claude stream lines into the user's dsh transcript. Requires an existing local adversary; no remote precondition.
- lowTool-permission bridge fails open when the dsh approval service is absent
lib/index.jsIn the supervised posture ('manual', labelled 每个工具问我) the plugin answers Claude's can_use_tool requests with allow without asking whenever ctx.get('approval') is undefined, i.e. whenever the deployment does not load an approval service. The user believes every tool call is confirmed, but every call is silently approved.
- lowLoopback guard trusts the client-supplied Host header
lib/index.jsisTrusted only inspects Host/Sec-Fetch-Site/Origin, which a non-browser client fully controls. It reliably blocks browser CSRF and DNS rebinding, but if dsh web is ever bound to a non-loopback interface a remote client can send `Host: 127.0.0.1` with no Origin and reach every RPC method (claude.command, claude.stop, claude.adopt, claude.preview, usage). No evidence in the harvested files that a non-loopback bind is possible; noted as hardening only.
Legit Claude Code bridge, but it places the user's OAuth token in curl argv, writes into a predictable unowned /tmp/ccmode tree, and fails open when no approval service is loaded.
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-11-11 · activity: Active
• Repo created: 2026-08-20
• Stars: ★ 3 · Forks: 2
• 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 claude-in-dsh?
claude-in-dsh 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 claude-in-dsh?
Run dsh plugin --profile web add github:GeekRicardo/claude-in-dsh#v1.3.0 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-19 (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.
