Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
Embeds a fixed-version code-server (VS Code Web) into DSH to follow the current workspace with custom port/path and hot switch.
- Embed fixed-version code-server (VS Code Web)
- Tracks current DSH workspace automatically
- Custom port/path and hot switching
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:yaodongH/dsh-vscode-bridgeInstall method: GitHub · runtime verified (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 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 | dsh 0.2.0-rc.1 |
|---|---|---|---|---|---|
| 8508b4 | ✓ | ✓ | ✓ | ✓ | ✓ |
8508b4github✓ 11 runtime-verified2026-10-19
https://github.com/yaodongH/dsh-vscode-bridge
✓dsh 0.2.1-rc.2current2026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/yaodongH/dsh-vscode-bridge (version unstated)
ID: dsh-vscode-bridge@8508b4@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
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-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/yaodongH/dsh-vscode-bridge (version unstated)
ID: dsh-vscode-bridge@8508b4@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
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-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/yaodongH/dsh-vscode-bridge (version unstated)
ID: dsh-vscode-bridge@8508b4@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-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.2.0-rc.22026-10-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/yaodongH/dsh-vscode-bridge (version unstated)
ID: dsh-vscode-bridge@8508b4@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-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.2.0-rc.12026-09-29L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/yaodongH/dsh-vscode-bridge (version unstated)
ID: dsh-vscode-bridge@8508b4@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
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/yaodongH/dsh-vscode-bridge (version unstated)
ID: dsh-vscode-bridge@8508b4@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.7-rc.12026-09-23not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/yaodongH/dsh-vscode-bridge (version unstated)
ID: dsh-vscode-bridge@8508b4@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
This level was not executed in this scan.
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/yaodongH/dsh-vscode-bridge (version unstated)
ID: dsh-vscode-bridge@8508b4@dsh0.1.6-alpha.2 · profile: l3-fullscan
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-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/yaodongH/dsh-vscode-bridge (version unstated)
ID: dsh-vscode-bridge@8508b4@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-23
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/yaodongH/dsh-vscode-bridge (version unstated)
ID: dsh-vscode-bridge@8508b4@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-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/yaodongH/dsh-vscode-bridge (version unstated)
ID: dsh-vscode-bridge@8508b4@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-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.
✓prehistory2026-10-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/yaodongH/dsh-vscode-bridge (version unstated)
ID: dsh-vscode-bridge@8508b4@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.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-vscode-bridge/)``[](https://www.dsh.so/artifact/dsh-vscode-bridge/)``[](https://www.dsh.so/artifact/dsh-vscode-bridge/)``[](https://www.dsh.so/artifact/dsh-vscode-bridge/)``[](https://www.dsh.so/artifact/dsh-vscode-bridge/)``[](https://www.dsh.so/artifact/dsh-vscode-bridge/)`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 — stricter wins → overall medium.
v0.1.23dsh manifest0.1.23git2026-10-210.1.23same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (12)
- warningnetIp · network
demo/e2e-focus-layout.mjs:8const TOKEN_URL = process.env.DSH_URL || 'http://127.0.0.1:3190/?token=<一次性启动 token>'; - warningnetIp · network
demo/e2e-focus-layout.mjs:54const API = 'http://127.0.0.1:3190'; - warningfsWrite · files
demo/e2e-focus-layout.mjs:68fs.writeFileSync(CFG, JSON.stringify(cfg, null, 2) + '\n'); - warningfsWrite · files
demo/e2e-focus-layout.mjs:326fs.writeFileSync(`${OUT}/e2e-results-0.1.23.json`, JSON.stringify({ when: new Date().toISOString(), results }, null, 1)); - warningnetIp · network
demo/e2e-instance-pool.mjs:6const TOKEN_URL = process.env.DSH_URL || 'http://127.0.0.1:3190/?token=<一次性启动 token>'; - warningfsWrite · files
demo/e2e-instance-pool.mjs:211fs.writeFileSync(`${OUT}/e2e-results-0.1.20.json`, JSON.stringify(results, null, 2)); - warningnetIp · network
demo/seed-dev-sessions.mjs:2const ORIGIN = 'http://127.0.0.1:3190'; - warningnetIp · network
lib/index.js:467if (await probe('http://127.0.0.1:' + config.port + '/healthz')) { healthy = true; break } - warningnetIp · network
lib/index.js:478console.log('dsh-vscode-bridge: code-server 就绪 http://127.0.0.1:' + config.port) - warningnetIp · network
lib/index.js:528server: rt.server ? { pid: rt.server.pid, port: config.port, url: 'http://127.0.0.1:' + config.port + '/', startedAt: rt.startedAt } : null, - warningnetIp · network
scripts/restart-dsh-web.sh:46curl -s -m 1 "http://127.0.0.1:$WEB_PORT/" >/dev/null 2>&1 && web_up=true - warningnetIp · network
scripts/restart-dsh-web.sh:47[ -n "$CS_PORT" ] && curl -s -m 1 "http://127.0.0.1:$CS_PORT/healthz" >/dev/null 2>&1 && cs_up=true
show 5 audit findings
- mediumcode-server is spawned with auth disabled on 127.0.0.1, giving any local process a full IDE terminal
lib/index.js:446The generated code-server.yaml disables authentication entirely, and the process listens on a fixed, guessable loopback port (default 18643). Any other local user or process on the host — and, via DNS-rebinding style browser tricks, potentially a web page — can open http://127.0.0.1:18643/ and obtain VS Code Web with an integrated terminal, i.e. arbitrary command execution as the DSH user, without any DSH token. DSH itself protects its UI with a token, so this is a strictly weaker boundary than the host it is embedded in.
- mediumBuilt-in web bundles are downloaded from a CDN without any integrity verification and written into the executed extension tree
lib/index.js:343Unlike the main tarball (whose sha256 is checked at line 253), every web-bundle file pulled from main.vscode-cdn.net is written verbatim into <install>/<PIN.root>/lib/vscode/extensions/** and then loaded by the workbench as extension code (browser entry points, plus Worker scripts named in WEB_BUNDLE_EXTRAS). A compromised or spoofed CDN response — or a MITM on a host with a hostile TLS trust store — yields code execution inside the code-server origin, which has full filesystem access via the code-server RPC, with no detection.
- mediumReserved-flag filter for extraArgs matches whole tokens only, so --auth=none / --bind-addr=0.0.0.0 bypasses it
lib/index.js:550'='-joined forms such as --bind-addr=0.0.0.0:18643, --auth=none, --user-data-dir=/somewhere or --extensions-dir=/somewhere are not equal to the listed flags and therefore pass, and are concatenated into the code-server argv after the --config yaml. This voids the guard the code claims to provide (it can override the 127.0.0.1/auth-none yaml and expose the unauthenticated IDE to the whole network). The precondition is write access to POST /dsh-vscode/config (any principal that can reach the DSH web UI's session).
- lowDefault configuration silently disables VS Code workspace trust for every opened directory
lib/index.js:698trustWorkspace defaults to true, so on every iframe boot the plugin writes security.workspace.trust.enabled=false into code-server's user settings.json, disabling Restricted Mode without a per-workspace prompt. Opening an untrusted repository (which the folder can be, since the opened directory follows the session cwd) then lets VS Code auto-run that repository's tasks/configuration and enable its extensions with the user's privileges — the exact scenario workspace trust exists to block.
- lowWorkspace-prefix check on installDir allows a recursive delete of sibling paths outside the bridge data directory
lib/index.js:258The validation is a string-prefix test, not a path-component test, so a value such as '<WORKSPACE>-backup' or '<WORKSPACE>/../<WORKSPACE>-old' (any absolute path whose text starts with WORKSPACE, always adjusted to a path outside .dsh/vscode-bridge) passes validConfig and is then passed to rmSync(-r -f) during ensureInstall, deleting an arbitrary tree. It also only throws after the download/verification steps, so the delete happens on the install path. Precondition: ability to POST /dsh-vscode/config (line 644) plus an install/ensure control call.
Plugin is mostly careful, but runs an unauthenticated loopback IDE, writes unverified CDN downloads into the executable install tree, and has a bypassable flag guard.
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-09-28 · activity: Active
• Repo created: 2026-08-30
• Stars: ★ 1 · 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).