Install verification: runtime verified (L5) · 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
VSCode Remote-SSH-like web plugin for remote development over SSH with file explorer and integrated terminal.
- SSH-based remote development
- Remote workspace access
- File explorer and integrated terminal
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 @zhangfengshun/dsh-remote-sshInstall method: GitHub · runtime verified (L5) · verified on dsh 0.2.2-rc.3
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-19) · 11 samples (roughly every 7 days), 5 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 11-18 · 11 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-28 → 11-18 · 10 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-11 → 11-17 · 61 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
09-11 → 11-18 · 62 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 1 requirement(s) across 3 @deepseek-ai/dsh-* packages. raw ranges
^0.1.0-rc.6 || ^0.1.5-rc.1 || ^0.1.7-rc.2 || ^0.2.0-rc.1 ×3
✓ Running dsh 0.2.2-rc.5 is within the declared range — install is not blocked by version.
Deciding channel: no engines.dsh declared, so every dsh* peer is checked (workspace:^ | ~ | * counts as the running version).
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| plugin \ dsh | dsh 0.2.2-rc.3 | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| 2.4.48 | ✓ | · | · | · | · |
| 2.4.47 | ✓ | · | · | · | · |
| 2.4.45 | · | ✓ | · | · | · |
| 2.4.44 | · | ✓ | · | · | · |
| 2.4.42 | · | · | · | · | · |
2.4.48npm✓ 1 runtime-verified2026-11-18
@zhangfengshun/dsh-remote-ssh
✓dsh 0.2.2-rc.32026-11-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: npm · @zhangfengshun/dsh-remote-ssh@2.4.48
ID: dsh-remote-ssh-2@2.4.48@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-18 · expires: 2026-11-25
View checks & evidence
active in loader tree (206 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
2.4.47npm✓ 1 runtime-verified2026-11-15
@zhangfengshun/dsh-remote-ssh
✓dsh 0.2.2-rc.32026-11-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: npm · @zhangfengshun/dsh-remote-ssh@2.4.47
ID: dsh-remote-ssh-2@2.4.47@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-15 · expires: 2026-11-22
View checks & evidence
active in loader tree (206 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
2.4.45npm✓ 1 runtime-verified2026-11-14
@zhangfengshun/dsh-remote-ssh
✓dsh 0.2.2-rc.12026-11-07L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · @zhangfengshun/dsh-remote-ssh@2.4.45
ID: dsh-remote-ssh-2@2.4.45@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-07 · expires: 2026-11-14
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.
2.4.44npm✓ 1 runtime-verified2026-11-04
@zhangfengshun/dsh-remote-ssh
✓dsh 0.2.2-rc.12026-11-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · @zhangfengshun/dsh-remote-ssh@2.4.44
ID: dsh-remote-ssh-2@2.4.44@dsh0.2.2-rc.1 · profile: l3-fullscan
Issued: 2026-11-04 · expires: 2026-11-11
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.
2.4.42npm2026-11-03
@zhangfengshun/dsh-remote-ssh
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
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-remote-ssh-2/?ref=badge)``[](https://www.dsh.so/artifact/dsh-remote-ssh-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-remote-ssh-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-remote-ssh-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-remote-ssh-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-remote-ssh-2/?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 medium (authoritative when present) → overall medium.
v2.1.1dsh manifestv2.1.1git2026-11-19v2.4.48version moved onclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (6)
- criticalsshWrite · destructive
lib/client.js:83"settings.keyPathPlaceholder": "~/.ssh/id_rsa", - criticalsshWrite · destructive
lib/client.js:183"settings.keyPathPlaceholder": "~/.ssh/id_rsa", - criticalshellExec · shell
lib/index.js:257async exec(cmd, stdinData) { - warningchildProcess · code-exec
lib/index.js:195const h = this.subprocess.spawn({ - warningchildProcess · code-exec
lib/index.js:295handle = subprocess.spawn({ - warningchildProcess · code-exec
lib/index.js:441return subprocess.spawn({ argv: argv, cwd: cwd || process.cwd(), stdio: stdio, graceMs: 60000 });
show 4 audit findings
- mediumStored SSH passwords are returned in clear by listProfiles API and the remote_ssh_profiles tool
lib/index.js:760ProfileSchema declares password with role('secret') (lib/index.js line 39), but settingsFace.read() returns the raw profile objects, so the plaintext password travels to browser JS via POST /remote-ssh/api/listProfiles and — because the remote_ssh_profiles tool returns settingsFace.read().profiles — into the model context, i.e. to the LLM provider and any transcript/log. Anyone with the page (XSS, devtools, extension) or a prompt that triggers the tool obtains reusable SSH credentials.
- lowUnquoted --include value interpolated into the remote grep command
lib/index.js:388The include value comes from the UI (OpsModal p2) and from the remote_ssh_grep tool parameter, and is concatenated unquoted into a command executed inside the persistent remote bash session (`{ cmd ; } 2>&1`). A value such as '*.py; id' breaks out and runs arbitrary commands on the remote host. Impact is bounded because the same plugin already exposes remote_ssh_exec / remoteExec, but it makes an allegedly search-only path an injection sink.
- lowSSH password passed on the sshpass command line
lib/index.js:285sshpass -p places the remote password in the process argv, readable by other local users via process listing and captured by OS audit/EDR logs for every connection, every CommandSession connect and every terminal. Combined with the plaintext storage in DSH settings, password auth leaks credentials outside the plugin's control.
- lowAuto-generated shell wrapper disables SSH host key verification
lib/index.jsThe wrapper written to ~/.dsh/remote-ssh/dsh-remote-shell.js and used as the shell for every remote workspace connects with StrictHostKeyChecking=no, unlike the main sshArgv which uses accept-new. An attacker in the network path can impersonate the remote host for terminal sessions, observing and altering commands and file contents.
Legitimate Remote-SSH plugin; ssh/tar subprocesses use argv arrays and remote paths are shell-quoted, but stored SSH passwords leak through API and tool output, plus minor 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-11-15 · activity: Active
• Repo created: 2026-08-18
• Stars: ★ 66 · Forks: 3
• 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).
Frequently asked questions
What is dsh-remote-ssh?
dsh-remote-ssh 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-remote-ssh?
Run dsh plugin --profile web add github:ZhangFengshun/dsh-remote-ssh#v2.1.1 in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4) plus web smoke testing (L5).
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-19 (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.
