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
Bridges DeepSeek Harness agent real-time status (sessions/tools/approvals) to a CodeIsland Dynamic Island panel.
- Real-time status bridging for DSH agents
- Shows sessions, tools, and approvals
- Integrates with CodeIsland Dynamic Island 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:cdxiaodong/dsh-island#v0.6.12Install 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.
7 samples (roughly every 7 days), 2 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-11 · 7 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-01 → 11-11 · 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.6.12 | ✗ | ✗ | ✗ | ✗ | ✗ |
v0.6.12github16 failed2026-11-16
https://github.com/cdxiaodong/dsh-island
✗dsh 0.2.2-rc.3current2026-11-16L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/cdxiaodong/dsh-island#v0.6.12
ID: dsh-island@v0.6.12@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-16 · expires: 2026-11-23
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-04L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/cdxiaodong/dsh-island#v0.6.12
ID: dsh-island@v0.6.12@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-04 · expires: 2026-11-11
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/cdxiaodong/dsh-island#v0.6.12
ID: dsh-island@v0.6.12@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-28L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/cdxiaodong/dsh-island#v0.6.12
ID: dsh-island@v0.6.12@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-28 · expires: 2026-11-04
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/cdxiaodong/dsh-island#v0.6.12
ID: dsh-island@v0.6.12@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-16L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/cdxiaodong/dsh-island#v0.6.12
ID: dsh-island@v0.6.12@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
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-10L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/cdxiaodong/dsh-island#v0.6.12
ID: dsh-island@v0.6.12@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
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-08L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/cdxiaodong/dsh-island#v0.6.12
ID: dsh-island@v0.6.12@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
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-29L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/cdxiaodong/dsh-island#v0.6.12
ID: dsh-island@v0.6.12@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
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-25L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/cdxiaodong/dsh-island#v0.6.12
ID: dsh-island@v0.6.12@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
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-21L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/cdxiaodong/dsh-island#v0.6.12
ID: dsh-island@v0.6.12@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-21 · expires: 2026-09-28
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/cdxiaodong/dsh-island#v0.6.12
ID: dsh-island@v0.6.12@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-13L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/cdxiaodong/dsh-island#v0.6.12
ID: dsh-island@v0.6.12@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-13 · expires: 2026-09-20
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-08L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/cdxiaodong/dsh-island#v0.6.12
ID: dsh-island@v0.6.12@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
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/cdxiaodong/dsh-island#v0.6.12
ID: dsh-island@v0.6.12@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.
✗prehistory2026-10-02L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/cdxiaodong/dsh-island#v0.6.12
ID: dsh-island@v0.6.12@dshunknown · profile: l4-sandbox
Issued: 2026-10-02 · expires: 2026-10-09
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-island/?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.6.12dsh manifestv0.6.12git2026-11-16v0.6.12same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (11)
- warningchildProcess · code-exec
lib/index.js:397const child = spawn(bin, [], { - warningshellExec · shell
lib/index.js:390execFile('open', [appPath], { env: { ...process.env, DSH_ISLAND_SOCKET_PATH: sock } }, () => { }); - warningshellExec · shell
scripts/demo.mjs:62await root.waterfall('tools/pre-execute', exec('call-1', 'git status --short'), ALLOW) - warningshellExec · shell
scripts/demo.mjs:63await root.waterfall('tools/post-execute', exec('call-1', 'git status --short'), { isError: false }, ACCEPT) - warningshellExec · shell
scripts/demo.mjs:67await root.waterfall('tools/pre-execute', exec('call-2', 'rm -rf node_modules'), ALLOW) - warningshellExec · shell
scripts/live-panel.mjs:116await root.waterfall('tools/pre-execute', exec('c1', 'git status --short'), ALLOW) - warningshellExec · shell
scripts/live-panel.mjs:117await root.waterfall('tools/post-execute', exec('c1', 'git status --short'), { isError: false }, ACCEPT) - warningshellExec · shell
scripts/live-panel.mjs:120await root.waterfall('tools/pre-execute', exec('c2', 'rm -rf node_modules'), ALLOW) - warningnetIp · network
scripts/live-panel.mjs:69console.log(`\x1b[1m[dsh-island live panel]\x1b[0m http://127.0.0.1:${PORT}`) - warningchildProcess · code-exec
src/index.ts:448const child = spawn(bin, [], { - warningshellExec · shell
src/index.ts:442execFile('open', [appPath], { env: { ...process.env, DSH_ISLAND_SOCKET_PATH: sock } }, () => {})
show 4 audit findings
- mediumApproval decisions and event data are trusted from an unauthenticated, predictable /tmp Unix socket
lib/socket.js:24available() accepts any file at the predictable /tmp path as 'the panel'; there is no peer-uid/credential check. A local process that owns that socket before the real panel starts is fed every event (PreToolUse/PostToolUse include tool_input, i.e. full command arguments, plus cwd/session ids) and its reply is the sole input to parseDecision(), which then returns {outcome:'allowed-once'}. Because the handler is registered with prepend=true, a hijacked socket can auto-approve arbitrary tool calls (e.g. shell commands) in the victim's DSH session, bypassing the real panel and other answerers.
- mediumControl socket executes plugin_disable/plugin_enable/menu_click for any local peer without authentication
lib/index.js:195Any process able to connect to the control socket can unload arbitrary plugins (disablePlugin calls registry.delete(entry.callback), enablePlugin re-registers saved callbacks), which can silently switch off security/audit plugins, and can invoke arbitrary menu callbacks registered by other plugins via menu_click. The endpoint is predictable and socket permissions depend on umask; DSH_ISLAND_CTL_SOCKET_PATH lets the endpoint be relocated to any path. No peer uid or message authentication is performed.
- lowPanel binary/app path is taken from config and launched with the full process environment
lib/index.jsArgument-array spawning without a shell is safe against injection, but config.panelBin is used unvalidated, so any party able to influence plugin config can make the process 'open' an arbitrary bundle/file at startup; the child also inherits the whole environment (including any secrets present in the DSH process env).
- lowDev-only live panel renders event fields into innerHTML without escaping
scripts/live-panel.mjsTool names/messages derived from DSH events (i.e. model-controlled) are injected into the DOM of the local demo page served on 127.0.0.1:3081; markup/script injected there runs in the demo page. This script is not part of the shipped plugin runtime (package.json files: lib, bin, panel), so impact is limited to developers running the demo.
No critical risk: the honest concerns are unauthenticated, predictable /tmp Unix sockets that carry approval decisions and plugin-control commands.
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-17 · activity: Inactive
• Repo created: 2026-08-15
• Stars: ★ 9 · Forks: 0
• Health: Inactive — no commit in 90+ days
Source
GitHub: github.com/cdxiaodong/dsh-island
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-island?
dsh-island 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-island?
Run dsh plugin --profile web add github:cdxiaodong/dsh-island#v0.6.12 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-16 (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.
