SSH for DeepSeek Harness agents: host address, port, account, password and private key live in an encrypted vault, and the conversation only ever uses an alias. The model never sees a password, and a password never reaches a command line or a remote process list.
Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it does
SSH for DeepSeek Harness agents: host address, port, account, password and private key live in an encrypted vault, and the conversation only ever uses an alias. The model never sees a password, and a password never reaches a command line or a remote process list.
Installation
dsh plugin --profile web add github:scientificmaniac/dsh-ssh-vault#v1.13.0Install 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 |
|---|---|---|
| v1.14.2 | · | · |
| v1.13.0 | ✓ | · |
v1.14.2github2026-10-21
https://github.com/scientificmaniac/dsh-ssh-vault
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
v1.13.0github✓ 1 runtime-verified2026-10-19
https://github.com/scientificmaniac/dsh-ssh-vault
✓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/scientificmaniac/dsh-ssh-vault#v1.13.0
ID: dsh-ssh-vault@v1.13.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
↳ carried from earlier record dsh-ssh-vault@v1.14.2@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-ssh-vault@v1.14.2@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-ssh-vault@v1.14.2@dsh0.2.1-rc.2 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per 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 official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-ssh-vault/)``[](https://www.dsh.so/artifact/dsh-ssh-vault/)`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.
v1.14.2dsh manifestv1.14.2git2026-10-21v1.14.2same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningchildProcess · code-exec
lib/ssh.js:294const child = spawn(exe, args, { - warningchildProcess · code-exec
lib/vault-api.js:167const child = spawn(command, args, { detached: true, stdio: 'ignore' }) - warningshellExec · shell
lib/vault-api.js:102execFile('icacls', [filePath, '/inheritance:r', '/grant:r', `${who}:(R)`], { windowsHide: true }, (error) => { - warningchildProcess · code-exec
lib/vault.js:88const child = spawn(exe, ['-NoProfile', '-NonInteractive', '-Command', script], { - warningbase64Decode · obfuscation
lib/vault.js:54+ "$b=[Convert]::FromBase64String($in);" - warningbase64Decode · obfuscation
lib/vault.js:70+ "$b=[Convert]::FromBase64String($in);"
show 2 audit findings
- mediumVault data key written as plain base64 with default file permissions in file/fallback mode
lib/vault.js:248keyProtection defaults to 'dpapi', which requires Windows PowerShell; on any non-Windows host (or if DPAPI fails) control reaches this branch and the AES-256 data key is written to key.json as plain base64 with no explicit mode (typically 0644 inside a 0755 vault dir, since mkdir is also called without a mode). Any other local user of the machine can then read key.json, decrypt vault.json, and recover every stored SSH password, sudo password and key passphrase. Uploaded private keys are correctly hardened with mode 0o600/icacls, so this is an inconsistency in the same codebase, not a platform
- lowSettings HTTP API validates only the method — no Origin/Sec-Fetch-Site or content-type check
lib/vault-api.js:340The handler performing save/remove/reveal/test validates nothing about the requester, and readJsonBody accepts any content-type as long as the bytes parse as JSON. If the host web server does not itself authenticate prefix routes, a page the user visits could send a no-preflight POST (text/plain content-type with a JSON body) to /ssh-vault/save or /ssh-vault/remove and add, alter or delete vault entries, or call reveal to learn internal host names and accounts. Impact is bounded because the response is not readable cross-origin and SameSite cookies usually block cross-site POSTs; client.js map
No backdoor or hidden exfiltration: ssh/scp subprocess use is intended and argv-safe, but the data key falls back to a plaintext file at default permissions off-Windows and the settings API checks no request origin.
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-10-19 · activity: Active
• Repo created: 2026-10-16
• 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).