Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
Data as of (UTC)
What it doesAI
VS Code sidebar for DeepSeek Harness with a native session tree, file and diff navigation, drag-to-reference, and clipboard/theme bridges.
- Native session tree inside the VS Code sidebar
- File and diff navigation for reviewing changes
- Drag-to-reference plus clipboard and theme bridges
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.
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); the npm pair from every snapshot.
4 samples (roughly every 7 days), 2 of them reconstructed (hollow dots); sampled points, not a daily series
09-17 → 10-19 · 4 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
Only 2 points (< 3): no chart yet
09-24 → 10-19 · 2 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
The snapshot’s last-week rolling window (official npm + npmmirror combined)
Only 0 points (< 3): no chart yet
no data yet
Installation
dsh plugin --profile web add github:Elevator14B/vscode-dsh-sidebar#v0.5.2Install method: GitHub · runtime test inconclusive (L5 unknown)
Verification & Compatibility○ Ecosystem plugin
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
package manifest not collected — the declared range is unknown.
| plugin ＼ dsh | dsh 0.2.1-rc.5 current | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| v0.5.2 | ○ | ○ | ○ | ○ | ○ |
| v0.4.0 | · | · | · | · | · |
| v0.3.13 | · | · | · | · | · |
| v0.3.12 | · | · | · | · | · |
v0.5.2github○ 7 ecosystem plugin2026-10-31
https://github.com/Elevator14B/vscode-dsh-sidebar
○dsh 0.2.1-rc.5current2026-10-31Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/Elevator14B/vscode-dsh-sidebar#v0.5.2
ID: vscode-dsh-sidebar@v0.5.2@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
not present in web-profile loader inventory
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-27Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/Elevator14B/vscode-dsh-sidebar#v0.5.2
ID: vscode-dsh-sidebar@v0.5.2@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
View checks & evidence
not present in web-profile loader inventory
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-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/Elevator14B/vscode-dsh-sidebar#v0.5.2
ID: vscode-dsh-sidebar@v0.5.2@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
not present in web-profile loader inventory
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-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/Elevator14B/vscode-dsh-sidebar#v0.5.2
ID: vscode-dsh-sidebar@v0.5.2@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
View checks & evidence
not present in web-profile loader inventory
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-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/Elevator14B/vscode-dsh-sidebar#v0.5.2
ID: vscode-dsh-sidebar@v0.5.2@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
not present in web-profile loader inventory
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-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/Elevator14B/vscode-dsh-sidebar#v0.5.2
ID: vscode-dsh-sidebar@v0.5.2@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-10-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/Elevator14B/vscode-dsh-sidebar#v0.5.2
ID: vscode-dsh-sidebar@v0.5.2@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.4.0github○ 1 ecosystem plugin2026-09-29
https://github.com/Elevator14B/vscode-dsh-sidebar
○dsh 0.2.0-rc.12026-09-29Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/Elevator14B/vscode-dsh-sidebar#v0.4.0
ID: vscode-dsh-sidebar@v0.4.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.3.13github○ 3 ecosystem plugin2026-09-26
https://github.com/Elevator14B/vscode-dsh-sidebar
○dsh 0.1.7-rc.22026-09-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/Elevator14B/vscode-dsh-sidebar#v0.3.13
ID: vscode-dsh-sidebar@v0.3.13@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
not present in web-profile loader inventory
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-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/Elevator14B/vscode-dsh-sidebar#v0.3.13
ID: vscode-dsh-sidebar@v0.3.13@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
not present in web-profile loader inventory
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-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/Elevator14B/vscode-dsh-sidebar#v0.3.13
ID: vscode-dsh-sidebar@v0.3.13@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.3.12github2026-09-16
https://github.com/Elevator14B/vscode-dsh-sidebar
Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L5 · Ecosystem 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/vscode-dsh-sidebar/?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 high (authoritative when present) → overall high.
—v0.5.2git2026-11-01v0.5.2same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningnetIp · network
scripts/smoke-browser.js:14res.end(`<meta http-equiv="Content-Security-Policy" content="default-src 'none'; frame-src http://127.0.0.1:*; connect-src http://127.0.0.1: - warningnetIp · network
scripts/smoke-browser.js:45await page.goto(`http://127.0.0.1:${server.address().port}/`) - warningshellExec · shell
src/process-tree.ts:86execFile('taskkill', ['/pid', String(this.root), '/T', '/F'], { windowsHide: true }, error => { - warningnetIp · network
src/proxy.ts:160return `http://127.0.0.1:${String(this.port)}` - warningchildProcess · code-exec
src/runtime-client.ts:189spawn(process.execPath, [keeperPath, '--cwd', canonicalCwd], { - warningchildProcess · code-exec
src/runtime-keeper.ts:190const spawned = spawn(launch.command, [...launch.args], {
show 3 audit findings
- highLoopback proxy injects the DSH session cookie for any local or cross-origin client without Origin/Host validation
src/proxy.ts:220DshBridgeProxy listens on 127.0.0.1 (default fixed port 39177) and is the only authentication boundary for the DSH backend: it overwrites Host/Origin with the backend's own values, defeating the backend's 'Origin must match Host' fence, and attaches the in-memory browser-session cookie to every request and every WebSocket upgrade (src/proxy.ts upgrade()). The incoming request's Origin is never checked and no per-window secret is required. Consequently any other local user/process can reach http://127.0.0.1:39177 and get fully authenticated access to the user's DSH agent (session RPCs, /api/rem
- mediumWorkspace-scoped dsh.embed.command/args are spawned verbatim, letting repository settings choose the executed binary
src/runtime.ts:59commandFor() reads the folder-scoped configuration, which includes the opened folder's .vscode/settings.json, and passes the values unchanged as LaunchSpec to the keeper, which spawns them with the user's full process.env and workspace cwd (src/runtime-keeper.ts start()). A malicious repository that sets dsh.embed.command to e.g. /bin/sh and dsh.embed.args to ["-c", "..."] therefore executes arbitrary commands with the user's credentials and environment as soon as the sidebar runtime starts in that (trusted) folder.
- lowUnconditional process-group SIGKILL can hit a reused pgid after group identity is lost
src/process-tree.ts:108sample() sets groupPresent=false when the root group is observed empty or the leader PID was reused, and then only known/descendant PIDs are tracked. However stop() still sends SIGKILL to the numeric process group -this.root whenever any tracked process is still live at the deadline. If that pgid has meanwhile been reused by an unrelated same-user group, the kill signal reaches stranger processes. The window is narrow (an uninterruptible tracked process outliving STOP_GRACE_MS plus a pgid reuse) but the effect is killing unrelated user processes.
The loopback bridge proxy authenticates every local client with the backend cookie and never checks Origin, so any local process or web page can drive the DSH agent.
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-09-29 · activity: Stable
• Repo created: 2026-09-16
• Stars: ★ 1 · 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 vscode-dsh-sidebar?
vscode-dsh-sidebar is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
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 vscode-dsh-sidebar?
Run dsh plugin --profile web add github:Elevator14B/vscode-dsh-sidebar#v0.5.2 in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs.
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-01 (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.