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
Bridges OpenCode free models (big-pickle, LongCat, MiMo, Nemotron, Space Bunny) into DSH's model selector as an opencode-xdbridge group.
- Adds OpenCode free models as an opencode-xdbridge group in DSH
- Visual interactive entry under Settings → OpenCode-XD
- Covers big-pickle, LongCat, MiMo, Nemotron, Space Bunny and more
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 dsh-opencode-xdbridgeInstall method: npm · 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.
current (registry 2026-11-10) · 8 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-30 → 11-09 · 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-12 → 11-09 · 5 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
10-01 → 11-11 · 40 points
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
10-01 → 11-14 · 42 points
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 a single engines.dsh range (decides alone; peerDependencies is not consulted). raw ranges
>=0.1.1-rc.1 <0.2.0
✗ 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-opencode-xdbridge@0.1.0 0.2.2-rc.3 (the exemption lives in the local profile; this site does not assume one)
Deciding channel: since 0.2.1-alpha.4 DSH judges by engines.dsh when declared — peerDependencies is then not consulted.
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 |
|---|---|---|---|---|---|
| 0.1.0 | · | · | ✓ | ✓ | ✓ |
0.1.0npm✓ 6 runtime-verified2026-11-14
dsh-opencode-xdbridge
✓dsh 0.2.1-rc.22026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-opencode-xdbridge@0.1.0
ID: dsh-opencode-xdbridge@0.1.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
↳ carried from earlier record dsh-opencode-xdbridge@0.1.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-opencode-xdbridge@0.1.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-opencode-xdbridge@0.1.0@dsh0.2.2-rc.3 (l3-fullscan)
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-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-opencode-xdbridge@0.1.0
ID: dsh-opencode-xdbridge@0.1.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
↳ carried from earlier record dsh-opencode-xdbridge@0.1.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-opencode-xdbridge@0.1.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-opencode-xdbridge@0.1.0@dsh0.2.2-rc.3 (l3-fullscan)
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-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-opencode-xdbridge@0.1.0
ID: dsh-opencode-xdbridge@0.1.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
↳ carried from earlier record dsh-opencode-xdbridge@0.1.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-opencode-xdbridge@0.1.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-opencode-xdbridge@0.1.0@dsh0.2.2-rc.3 (l3-fullscan)
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: npm · dsh-opencode-xdbridge@0.1.0
ID: dsh-opencode-xdbridge@0.1.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
↳ carried from earlier record dsh-opencode-xdbridge@0.1.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-opencode-xdbridge@0.1.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-opencode-xdbridge@0.1.0@dsh0.2.2-rc.3 (l3-fullscan)
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.12026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-opencode-xdbridge@0.1.0
ID: dsh-opencode-xdbridge@0.1.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
↳ carried from earlier record dsh-opencode-xdbridge@0.1.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-opencode-xdbridge@0.1.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-opencode-xdbridge@0.1.0@dsh0.2.2-rc.3 (l3-fullscan)
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: npm · dsh-opencode-xdbridge@0.1.0
ID: dsh-opencode-xdbridge@0.1.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
↳ carried from earlier record dsh-opencode-xdbridge@0.1.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-opencode-xdbridge@0.1.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-opencode-xdbridge@0.1.0@dsh0.2.2-rc.3 (l3-fullscan)
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-opencode-xdbridge/?ref=badge)``[](https://www.dsh.so/artifact/dsh-opencode-xdbridge/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-opencode-xdbridge/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-opencode-xdbridge/?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 low (authoritative when present) → overall low.
v0.1.0dsh manifest0.1.0npm2026-11-140.1.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (8)
- criticalshellExec · shell
lib/runtime.js:92const { stdout } = await exec(file, ['--version'], { timeout: 15000, windowsHide: true }) - warningfsWrite · files
lib/index.js:69return fs.createWriteStream(file, { flags: 'a', mode: 0o600 }) - warningchildProcess · code-exec
lib/runtime.js:280const child = spawn(binary, ['serve', '--pure', '--hostname', '127.0.0.1', '--port', String(port)], { - warningnetIp · network
lib/runtime.js:289const backend = new Backend(`http://127.0.0.1:${port}`, password, undefined, message => { - warningfsWrite · files
lib/runtime.js:140await fs.chmod(`${target}.tmp`, 0o755) - warningfsWrite · files
lib/runtime.js:189await fs.chmod(target, 0o755) - warningnetIp · network
lib/shim.js:105const route = new URL(req.url, 'http://127.0.0.1').pathname - warningnetIp · network
lib/shim.js:222origin = `http://127.0.0.1:${server.address().port}`
show 3 audit findings
- lowRuntime resolution executes any configured binaryPath/OPENCODE_BINARY_PATH before validating the file
lib/runtime.js:92The candidate list is `options.candidates ?? [process.env.OPENCODE_BINARY_PATH, ~/.opencode/bin/opencode, /opt/homebrew/bin/opencode, /usr/local/bin/opencode]` and the version-named directories under <dataDir>/runtime are also executed to read their version. The file is executed first; only its stdout must then match VERSION_PATTERN. Whoever can set the plugin config (binaryPath) or that env var — or write a directory into a world-readable dataDir — gets code execution as the DSH user at plugin startup. Precondition is a local write/config capability, so this is a hardening gap rather than a r
- lowState-changing plugin routes accept requests without an Origin header
lib/web-status.js:51POST /plugins/dsh-opencode-xdbridge/runtime/restart, /models/probe and /models/refresh are protected only by this Origin check (browsers always send Origin cross-origin, so page-based CSRF is blocked). Any local process — or a remote client if the host web server is ever bound beyond loopback — can therefore restart the managed runtime (interrupting in-flight inference) or trigger a full probe sweep that consumes upstream free-tier quota. No data is exposed by these routes.
- lowSecurity-critical modules lib/backend.js and lib/client.js are referenced but missing from the audit bundle
lib/index.jsThe bundle claims NOT_HARVESTED is empty, yet backend.js (which performs the runtime call, the permission-request handling that refuses native tool execution, and its handoff to external tool calls) and the browser client are absent. The plugin's core safety claim — that native operations are only ever 'asked' and then refused by the bridge, so nothing runs in the isolated runtime — cannot be verified from the reviewed code.
Static-scan critical refuted: no reachable high-risk flaw; the vendor-binary download is sha512-verified and the loopback shim is token-guarded, leaving only low hardening gaps.
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-10-09 · activity: Stable
• Repo created: 2026-09-29
• Stars: ★ 16 · Forks: 2
• 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 @XDTrees/dsh-opencode-xdbridge?
@XDTrees/dsh-opencode-xdbridge 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 @XDTrees/dsh-opencode-xdbridge?
Run dsh plugin --profile web add dsh-opencode-xdbridge 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-14 (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.