DSH plugin developer sandbox: spawn isolated DeepSeek Harness web mirror instances (own DSH_HOME/port/profile) that mount the plugin under development, with optional host API/model inheritance. GUI panel + sandbox_* agent tools.
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
Plugin developer sandbox spawning isolated DSH web mirror instances with own config, mounting plugin under development, optional API/model inheritance, GUI panel and sandbox tools.
- Spawns isolated DSH web mirror instances (own DSH_HOME/port/profile)
- Mounts plugin under development for testing
- GUI panel + sandbox_* agent tools with optional host API inheritance
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:zp-home/dsh-dev-sandbox#v0.1.0Install method: GitHub · sandbox install failed (L4) · verified on dsh 0.2.1-rc.5
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.
9 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-17 → 11-15 · 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-24 → 11-15 · 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
Based on 1 requirement(s) across 5 @deepseek-ai/dsh-* packages. raw ranges
^0.1.0-rc.6 ×5
✗ Running dsh 0.2.2-rc.3 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-dev-sandbox@0.1.0 0.2.2-rc.3 (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 |
|---|---|---|---|---|---|
| v0.1.0 | ✗ | ✗ | ✓ | ✓ | ✓ |
v0.1.0github✓ 13 runtime-verified2 failed2026-11-14
https://github.com/zp-home/dsh-dev-sandbox
✗dsh 0.2.1-rc.52026-11-01L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/zp-home/dsh-dev-sandbox#v0.1.0
ID: dsh-dev-sandbox@v0.1.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
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.2.1-rc.32026-10-28L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/zp-home/dsh-dev-sandbox#v0.1.0
ID: dsh-dev-sandbox@v0.1.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-28 · expires: 2026-11-04
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.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/zp-home/dsh-dev-sandbox#v0.1.0
ID: dsh-dev-sandbox@v0.1.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/zp-home/dsh-dev-sandbox#v0.1.0
ID: dsh-dev-sandbox@v0.1.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-12L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/zp-home/dsh-dev-sandbox#v0.1.0
ID: dsh-dev-sandbox@v0.1.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
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/zp-home/dsh-dev-sandbox#v0.1.0
ID: dsh-dev-sandbox@v0.1.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.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/zp-home/dsh-dev-sandbox#v0.1.0
ID: dsh-dev-sandbox@v0.1.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/zp-home/dsh-dev-sandbox#v0.1.0
ID: dsh-dev-sandbox@v0.1.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/zp-home/dsh-dev-sandbox#v0.1.0
ID: dsh-dev-sandbox@v0.1.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/zp-home/dsh-dev-sandbox#v0.1.0
ID: dsh-dev-sandbox@v0.1.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/zp-home/dsh-dev-sandbox#v0.1.0
ID: dsh-dev-sandbox@v0.1.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/zp-home/dsh-dev-sandbox#v0.1.0
ID: dsh-dev-sandbox@v0.1.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/zp-home/dsh-dev-sandbox#v0.1.0
ID: dsh-dev-sandbox@v0.1.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/zp-home/dsh-dev-sandbox#v0.1.0
ID: dsh-dev-sandbox@v0.1.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/zp-home/dsh-dev-sandbox#v0.1.0
ID: dsh-dev-sandbox@v0.1.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/dsh-dev-sandbox/?ref=badge)``[](https://www.dsh.so/artifact/dsh-dev-sandbox/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-dev-sandbox/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-dev-sandbox/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-dev-sandbox/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-dev-sandbox/?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 medium (authoritative when present) → overall medium.
v0.1.0dsh manifestv0.1.0git2026-11-17v0.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (8)
- warningchildProcess · code-exec
lib/index.js:415const result = spawnSync(pnpmPath, ["run", "build"], { - warningchildProcess · code-exec
lib/index.js:532const child = spawn(nodeExec, [ - warningchildProcess · code-exec
lib/index.js:616if (process.platform === "win32") spawnSync("taskkill", [ - warningnetIp · network
lib/index.js:588url: `http://127.0.0.1:${spawnPort}`, - warningchildProcess · code-exec
src/manager.ts:440const result = spawnSync(pnpmPath, ['run', 'build'], { - warningchildProcess · code-exec
src/manager.ts:594const child = spawn( - warningchildProcess · code-exec
src/manager.ts:677spawnSync('taskkill', ['/PID', String(child.pid), '/T', '/F'], { windowsHide: true, stdio: 'ignore' }) - warningnetIp · network
src/manager.ts:638url: `http://127.0.0.1:${spawnPort}`,
show 6 audit findings
- mediumPrivileged sandbox API is exposed on the web server with no authentication/authorization checks
src/routes.ts:61dispatch() gates every action only by HTTP method; any client that can reach the dsh web port can call POST /api/dsh-dev-sandbox/build (-> manager.build -> spawnSync('pnpm',['run','build'],{cwd}) executing package.json scripts.build of any caller-supplied directory), POST /create + /start (spawns a harness process that mounts attacker-chosen plugin code), and POST /destroy (recursive delete). Because the body is parsed regardless of Content-Type, a cross-origin 'simple request' POST (text/plain) from a visited web page is not blocked by preflight, so CSRF against localhost is possible if the h
- mediumUnvalidated plugin package name is used as path segments when creating the profile junction
src/manager.ts:533packageName comes straight from the scanned plugin's package.json (scanPlugin only requires it to be a string plus a dsh.bundle.patch). A name such as '../../../../some/dir' makes `link` resolve outside the sandbox home; ensurePluginJunction then rmSync({recursive:true,force:true})s any existing symlink there and symlinkSync()s a junction to the caller-chosen target, i.e. an HTTP/tool caller can create or replace symlinks at arbitrary paths, and the same name is written as a dependency key into the generated profile package.json.
- mediumSandbox name is not validated outside create(), allowing recursive deletion of caller-chosen paths
src/manager.ts:690NAME_PATTERN is enforced only in create(); get/start/stop/logs/destroy take `name` from the HTTP body or tool argument and homeOf(name) is a plain join(homeRoot, name). POST /api/dsh-dev-sandbox/destroy with name='../../<dir>' reaches rmSync({recursive:true,force:true}) on that directory. The path is constrained by destroy()->stop()->get() requiring a parseable sandbox-state.json in the target directory (and by the attacker already being able to place files), but once satisfied it is an arbitrary recursive directory delete.
- mediumSandbox children inherit the full host environment plus host DEEPSEEK credentials
src/manager.ts:580Every sandbox child runs with a copy of the host process environment, and when inheritHostApi is true (default) collectHostApiEnv() additionally reads ~/.dsh/.env and ~/.dsh/.credentials.yaml and injects DEEPSEEK_API_KEY/BASE_URL. The child then mounts the plugin under development — i.e. arbitrary third-party code — which can read these values (and the host settings.yaml copied by inheritHostSettings) despite the sandbox being advertised as isolated from the dev host.
- lowRoute /scan lets any caller probe arbitrary filesystem paths
src/routes.ts:95scanPlugin() resolves an arbitrary caller-supplied path, reports the directory exists (via the package.json requirement), echoes resolved path/name/version and probes existence of the manifest's `main` and lib/client.js (GET /scan?path=...). This is a filesystem existence oracle for a caller that should not have one.
- lowPlugin injects a self-authored section into the agent system prompt
src/index.ts:78When announceToAgent is true (default) the plugin unconditionally adds third-party-authored text to the host system prompt, advertising its tools and instructing the model when to treat the user's words as referring to this plugin. It does not override safety rules, but it is unverified plugin-controlled model guidance that biases agent tool selection.
Dev-sandbox plugin: unauthenticated privileged /api routes, unvalidated names in rmSync/junction paths, and host env + API keys inherited by spawned sandbox processes.
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-08-21 · activity: Stable
• Repo created: 2026-08-16
• Stars: ★ 2 · 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 dsh-dev-sandbox?
dsh-dev-sandbox 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-dev-sandbox?
Run dsh plugin --profile web add github:zp-home/dsh-dev-sandbox#v0.1.0 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-17 (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.
