Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it does
Give DeepSeek Harness its own persistent computer: a bundled microVM with shell, browser, live view and approval gates
Installation
dsh plugin --profile web add github:Kevinwu901113/dsh-computerInstall method: GitHub · sandbox install ok, web smoke failed (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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.1-rc.2 current |
|---|---|
| 3cf313 | ✗ |
3cf313github1 failed2026-10-18
https://github.com/Kevinwu901113/dsh-computer
✗dsh 0.2.1-rc.2current2026-10-18L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/Kevinwu901113/dsh-computer (version unstated)
ID: dsh-computer-2@3cf313@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-computer-2/)`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 no conclusion — stricter wins → overall low.
v0.5.0dsh manifest0.5.0git2026-10-210.5.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (3)
- warningshellExec · shell
src/backends/proxy.js:10const out = execFileSync('scutil', ['--proxy'], { encoding: 'utf8', timeout: 3000 }); - warningshellExec · shell
src/backends/proxy.js:16const out = execFileSync('reg', ['query', key], { encoding: 'utf8', timeout: 3000 }); - warningchildProcessImport · code-exec
src/docker.js:3import { execFile } from 'node:child_process';
not in the dynamic queue (queue only covers plugins static-flagged at warn or above) — this does not mean the dynamic audit found it safe.
Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.
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-17 · activity: Active
• Repo created: 2026-10-14
• Stars: ★ 0 · 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).
