Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.3 · last checked Install verification details →
What it does
Multi-host SSH toolbelt for DeepSeek Harness: server registry, /ssh, run/put/get tools, destructive-command guard, secret redaction, audit log
Installation
dsh plugin --profile web add dsh-plugin-ssh-remoteInstall 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
package manifest not collected — the declared range is unknown.
| plugin \ dsh | dsh 0.2.1-rc.3 current |
|---|---|
| 0.1.0 | ✓ |
| v0.1.0 | ◐ |
0.1.0npm✓ 1 runtime-verified2026-10-28
dsh-plugin-ssh-remote
✓dsh 0.2.1-rc.3current2026-10-28L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-plugin-ssh-remote@0.1.0
ID: dsh-plugin-ssh-remote@0.1.0@dsh0.2.1-rc.3 · profile: l5-web-smoke
Issued: 2026-10-28 · expires: 2027-01-26
View checks & evidence
↳ carried from earlier record dsh-plugin-ssh-remote@v0.1.0@dsh0.2.1-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-plugin-ssh-remote@v0.1.0@dsh0.2.1-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-plugin-ssh-remote@v0.1.0@dsh0.2.1-rc.3 (l4-sandbox)
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.0github◐ 1 testing2026-10-28
https://github.com/IVAN4242/dsh-plugin-ssh-remote
◐dsh 0.2.1-rc.3current2026-10-28L4 · testing (install passed, runtime untested)
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/IVAN4242/dsh-plugin-ssh-remote#v0.1.0
ID: dsh-plugin-ssh-remote@v0.1.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-28 · expires: 2026-11-04
View checks & evidence
↳ carried from earlier record dsh-plugin-ssh-remote@v0.1.0@dsh0.2.1-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-plugin-ssh-remote@v0.1.0@dsh0.2.1-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-plugin-ssh-remote@v0.1.0@dsh0.2.1-rc.3 (l4-sandbox)
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.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-plugin-ssh-remote/)``[](https://www.dsh.so/artifact/dsh-plugin-ssh-remote/)`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 no conclusion (static stands) → overall low.
v0.1.0dsh manifestv0.1.0git2026-10-28v0.1.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (5)
- criticaldestructiveRm · destructive
index.js:378'Catastrophic commands (rm -rf /, mkfs, dd to a device) are still refused.', - criticalsshWrite · destructive
registry.js:88`"${path}" does not look like a path to a private key. Give a path such as ~/.ssh/id_ed25519, ` + - warningchildProcess · code-exec
acl.js:81child = spawn(argv[0], argv.slice(1), { stdio: 'ignore', windowsHide: true }) - warningchildProcess · code-exec
e2e-live.mjs:51spawn(spec) { - warningchildProcess · code-exec
e2e-live.mjs:58const child = spawn(program, rest, {
not in the dynamic queue (the queue only covers plugins whose static tier is medium or above — medium/high/critical; since 2026-10-24 entries rated low are not audited even when dsh-only rules logged warnings) — this does not mean the dynamic audit found it safe.
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-27 · activity: Active
• Repo created: 2026-10-27
• Stars: ★ 0 · 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).
