Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.2-rc.3 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Process-isolated sandbox for testing DSH plugins safely, with an enforced merge gate.
- Runs each test in isolated process, data, and port
- Merge gate: whitelist, syntax/bundle checks, rollback
- Crashes stay in sandbox; main instance unaffected
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:Sutera-Diffusus/dsh-sandbox-tester#v0.1.0Install method: GitHub · sandbox install ok, web smoke failed (L5)
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.
8 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-13 · 8 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
10-06 → 11-13 · 6 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 current | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| v0.1.0 | ✗ | ✗ | ✗ | ✗ | ✗ |
v0.1.0github18 failed2026-11-17
https://github.com/Sutera-Diffusus/dsh-sandbox-tester
✗dsh 0.2.2-rc.3current2026-11-17L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/Sutera-Diffusus/dsh-sandbox-tester#v0.1.0
ID: dsh-sandbox-tester@v0.1.0@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-17 · expires: 2026-11-24
View checks & evidence
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-05L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/Sutera-Diffusus/dsh-sandbox-tester#v0.1.0
ID: dsh-sandbox-tester@v0.1.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-rc.52026-10-31L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/Sutera-Diffusus/dsh-sandbox-tester#v0.1.0
ID: dsh-sandbox-tester@v0.1.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/Sutera-Diffusus/dsh-sandbox-tester#v0.1.0
ID: dsh-sandbox-tester@v0.1.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
View checks & evidence
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-19L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/Sutera-Diffusus/dsh-sandbox-tester#v0.1.0
ID: dsh-sandbox-tester@v0.1.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
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-17L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/Sutera-Diffusus/dsh-sandbox-tester#v0.1.0
ID: dsh-sandbox-tester@v0.1.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
View checks & evidence
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/Sutera-Diffusus/dsh-sandbox-tester#v0.1.0
ID: dsh-sandbox-tester@v0.1.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
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/Sutera-Diffusus/dsh-sandbox-tester#v0.1.0
ID: dsh-sandbox-tester@v0.1.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/Sutera-Diffusus/dsh-sandbox-tester#v0.1.0
ID: dsh-sandbox-tester@v0.1.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/Sutera-Diffusus/dsh-sandbox-tester#v0.1.0
ID: dsh-sandbox-tester@v0.1.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/Sutera-Diffusus/dsh-sandbox-tester#v0.1.0
ID: dsh-sandbox-tester@v0.1.0@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
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/Sutera-Diffusus/dsh-sandbox-tester#v0.1.0
ID: dsh-sandbox-tester@v0.1.0@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/Sutera-Diffusus/dsh-sandbox-tester#v0.1.0
ID: dsh-sandbox-tester@v0.1.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/Sutera-Diffusus/dsh-sandbox-tester#v0.1.0
ID: dsh-sandbox-tester@v0.1.0@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
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-09L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/Sutera-Diffusus/dsh-sandbox-tester#v0.1.0
ID: dsh-sandbox-tester@v0.1.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-16
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/Sutera-Diffusus/dsh-sandbox-tester#v0.1.0
ID: dsh-sandbox-tester@v0.1.0@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/Sutera-Diffusus/dsh-sandbox-tester#v0.1.0
ID: dsh-sandbox-tester@v0.1.0@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-10-04L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/Sutera-Diffusus/dsh-sandbox-tester#v0.1.0
ID: dsh-sandbox-tester@v0.1.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
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-sandbox-tester/?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 manifestv0.1.0git2026-11-17v0.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (7)
- warningchildProcess · code-exec
lib/merge-gate.js:154const child = spawn(process.execPath, ['--check', file], { - warningchildProcess · code-exec
lib/proctree.js:140const child = spawn('node', [bin, 'web', '--port', String(meta.port)], { - warningshellExec · shell
lib/tools-lifecycle.js:106execFile('robocopy', args, { windowsHide: true, maxBuffer: 16 * 1024 * 1024 }, (error, stdout, stderr) => { - warningchildProcess · code-exec
lib/tools-runhealth.js:179const child = spawn(process.execPath, [script, String(meta.port), String(meta.name || '')], { - warningnetIp · network
lib/tools-runhealth.js:35const BODY_URL = 'http://127.0.0.1:3080/' // 本体固定端口,永不占用 - warningnetIp · network
lib/tools-runhealth.js:278const poll = await pollHttp200(`http://127.0.0.1:${meta.port}/`, POLL_TIMEOUT_MS) - warningnetIp · network
lib/tools-runhealth.js:371const status = await httpStatus(`http://127.0.0.1:${meta.port}/`)
show 6 audit findings
- mediumSandbox child processes inherit the full host environment (tokens/API keys)
lib/proctree.js:154Any code placed into a sandbox via sandbox_inject and started with sandbox_run runs with the host user's full environment, including DSH credentials and other secrets, so the 'isolated' test instance can read and exfiltrate them.
- mediumsandbox_inject 'source' accepts any absolute host path (arbitrary file read into sandbox)
lib/tools-lifecycle.js:442Path confinement (resolveWithinProgram) covers only the destination; the source may be any file readable by the host process, so credentials/config outside the sandbox can be copied into a program tree that is later executed by sandbox_run.
- mediumsandbox_merge allows any non-existing path under the body root and arbitrary src; writes production files when MERGE_ALLOW=1
lib/merge-gate.js:105Once DSH_SANDBOX_MERGE_ALLOW=1 is set (required for the feature at all), agent-supplied targets can create arbitrary new files inside D:\Deepseek harness or overwrite the 11 whitelisted host modules (agent-loop, host-apiproxy, ...) with content read from any host path; the only content validation is node --check and a '<html>' substring test, so a manipulated model prompt can persist host-side code.
- lowsandbox_prune recursively deletes using registry-provided name without re-validation
lib/tools-lifecycle.js:572Names are validated only at create time; loadRegistry returns D:\ai-temp\dsh-sandbox-registry.json unvalidated, so a tampered record name such as '..' makes join(SANDBOX_ROOT, name) escape and prune can delete arbitrary directories.
- lowQA runner spawns node on a script path taken from DSH_SANDBOX_QA_SCRIPT / injected constants
lib/tools-runhealth.js:125Whoever controls the host environment (or the injected services.constants.qaScript) can make sandbox_run execute an arbitrary file with node; precondition is host-level env control, so impact is limited.
- lowinstall.mjs in-place patches a third-party installed host file (dsh-host-apiproxy/lib/index.js)
install.mjs:171The installer edits another installed program's source to add a settings namespace; it backs up first and is idempotent, but patching node_modules in place can conflict with package integrity and future updates.
Sandbox-orchestrator plugin: tool paths are mostly validated, but sandbox children inherit host env secrets, inject reads arbitrary host files, and merge can write production-body files when enabled.
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-16 · activity: Inactive
• Repo created: 2026-08-16
• Stars: ★ 5 · Forks: 0
• Health: Inactive — no commit in 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-sandbox-tester?
dsh-sandbox-tester 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-sandbox-tester?
Run dsh plugin --profile web add github:Sutera-Diffusus/dsh-sandbox-tester#v0.1.0 in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4); the web smoke test (L5) has not passed 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.
