Install verification: runtime test inconclusive (L5 unknown) · 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
Docker container sandbox plugin with 39 tools, snapshots, file transfer, port forwarding, background tasks, audit, quotas, network policies, and native UI.
- 39 docker_* model tools
- Snapshot/rollback and quotas
- File transfer and port forwarding
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:GHJIVHIDD/dsh-plugin-container#v1.0.3Install method: GitHub · runtime test inconclusive (L5 unknown)
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.
10 samples (roughly every 7 days), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-17 → 11-16 · 10 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-16 · 9 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 |
|---|---|---|---|---|---|
| v1.0.3 | ○ | ✓ | ✓ | ✓ | ✓ |
v1.0.3github✓ 15 runtime-verified2026-11-14
https://github.com/GHJIVHIDD/dsh-plugin-container
○dsh 0.2.2-rc.3current2026-11-14not tested
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/GHJIVHIDD/dsh-plugin-container#v1.0.3
ID: dsh-plugin-container@v1.0.3@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-14 · expires: 2026-11-21
View checks & evidence
inventory probe failed (rpc-error) — inconclusive, not a plugin verdict (reinterpreted 2026-11-17)
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/GHJIVHIDD/dsh-plugin-container#v1.0.3
ID: dsh-plugin-container@v1.0.3@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/GHJIVHIDD/dsh-plugin-container#v1.0.3
ID: dsh-plugin-container@v1.0.3@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/GHJIVHIDD/dsh-plugin-container#v1.0.3
ID: dsh-plugin-container@v1.0.3@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/GHJIVHIDD/dsh-plugin-container#v1.0.3
ID: dsh-plugin-container@v1.0.3@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/GHJIVHIDD/dsh-plugin-container#v1.0.3
ID: dsh-plugin-container@v1.0.3@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/GHJIVHIDD/dsh-plugin-container#v1.0.3
ID: dsh-plugin-container@v1.0.3@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/GHJIVHIDD/dsh-plugin-container#v1.0.3
ID: dsh-plugin-container@v1.0.3@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/GHJIVHIDD/dsh-plugin-container#v1.0.3
ID: dsh-plugin-container@v1.0.3@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.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/GHJIVHIDD/dsh-plugin-container#v1.0.3
ID: dsh-plugin-container@v1.0.3@dsh0.1.6-alpha.2 · profile: l4-sandbox
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/GHJIVHIDD/dsh-plugin-container#v1.0.3
ID: dsh-plugin-container@v1.0.3@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/GHJIVHIDD/dsh-plugin-container#v1.0.3
ID: dsh-plugin-container@v1.0.3@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/GHJIVHIDD/dsh-plugin-container#v1.0.3
ID: dsh-plugin-container@v1.0.3@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/GHJIVHIDD/dsh-plugin-container#v1.0.3
ID: dsh-plugin-container@v1.0.3@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/GHJIVHIDD/dsh-plugin-container#v1.0.3
ID: dsh-plugin-container@v1.0.3@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/GHJIVHIDD/dsh-plugin-container#v1.0.3
ID: dsh-plugin-container@v1.0.3@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-plugin-container/?ref=badge)``[](https://www.dsh.so/artifact/dsh-plugin-container/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-plugin-container/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-plugin-container/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-plugin-container/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-plugin-container/?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.
v1.0.3dsh manifestv1.0.3git2026-11-17v1.0.3same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningchildProcess · code-exec
dsh-plugin-container/lib/index.js:792const proc = spawn(DOCKER, ['logs', '-f', '--tail', '200', '--timestamps', name], { - warningbase64Decode · obfuscation
dsh-plugin-container/lib/index.js:1436"printf '%s' '" + commandB64 + "' | base64 -d > " + dir + '/cmd.sh', - warningbase64Decode · obfuscation
dsh-plugin-container/lib/index.js:1437"printf '%s' '" + runB64 + "' | base64 -d > " + dir + '/run.sh', - warningchildProcess · code-exec
dsh-plugin-container/src/index.js:792const proc = spawn(DOCKER, ['logs', '-f', '--tail', '200', '--timestamps', name], { - warningbase64Decode · obfuscation
dsh-plugin-container/src/index.js:1436"printf '%s' '" + commandB64 + "' | base64 -d > " + dir + '/cmd.sh', - warningbase64Decode · obfuscation
dsh-plugin-container/src/index.js:1437"printf '%s' '" + runB64 + "' | base64 -d > " + dir + '/run.sh',
show 4 audit findings
- highdocker_cli passes arbitrary argv to the Docker CLI, bypassing the plugin's ownership/permission model
dsh-plugin-container/lib/index.jsThis tool performs no canExec/canManage/assertOwner check and no argument filtering, so any session can run `docker run --privileged -v /:/host ...`, `docker exec` into other sessions' containers, or `docker rm -f` them, defeating the documented share/policy sandbox. Because the daemon is normally root, a privileged bind mount of `/` is host root compromise reachable from a single model tool call (and thus from prompt-injected content).
- highUnauthenticated /dock-api routes trust the client-supplied session and can create containers with host mounts and commands
dsh-plugin-container/lib/index.jsThese routes are plain GET handlers with no token, Origin or session-ownership check; `session` comes straight from the query string and is used for authorization elsewhere (e.g. createSnapshot/audit). Anyone who can reach the local web server — including a malicious web page issuing a cross-origin GET (CSRF), since the request has side effects and needs no body — can create a container with `volumes=/:/host` and `command`, then read/write the host filesystem, or call /dock-api/op?action=rm to delete containers.
- mediumdocker_create/docker_run pass volumes straight to -v, allowing arbitrary host bind mounts such as /:/host
dsh-plugin-container/lib/index.jsUnlike docker_build and docker_upload/download, which force local paths under the workspace (resolveLocalPath), container bind mounts are not validated at all. A model-generated or prompt-injected `volumes: ["/:/host"]` (also reachable through the panel create route) yields read-write root access to the host filesystem from inside the 'sandbox', i.e. an escape of the isolation the plugin advertises.
- mediumSeveral tools and panel read routes access other sessions' containers without the ownership model, exposing env vars and logs
dsh-plugin-container/lib/index.jscanExec/canManage default-allow any container without a state record, and docker_logs/docker_inspect/docker_stats/docker_network/docker_rmi/docker_volume use raw identifiers with no check at all; the panel routes /dock-api/inspect, /dock-api/logs, /dock-api/shell and /dock-api/jobs also perform no permission check. Any session (or any caller of the local HTTP routes) can therefore read another session's container environment (inspect returns full cfg.Env), logs and shell history, disconnect its networks, or delete its snapshot images.
Docker sandbox plugin uses execFile (no host shell) but ships an unrestricted docker_cli passthrough, unauthenticated /dock-api routes and arbitrary bind mounts, enabling host takeover.
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-20 · activity: Stable
• Repo created: 2026-08-15
• Stars: ★ 3 · 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-plugin-container?
dsh-plugin-container 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-plugin-container?
Run dsh plugin --profile web add github:GHJIVHIDD/dsh-plugin-container#v1.0.3 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.
