Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
Drive and control the dsh instances running on your other machines from a single local window.
- One local window to drive all your dsh machines
- Remote, multi-machine control of dsh instances
- Built for multi-machine dsh setups
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 github:6mt/dsh-control#v0.2.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
package manifest not collected — the declared range is unknown.
| plugin \ dsh | dsh 0.2.1-rc.2 current | dsh 0.2.1-alpha.2 |
|---|---|---|
| v0.2.1 | · | · |
| v0.2.0 | ✓ | · |
| v0.1.1 | · | · |
| v0.1.0 | · | ✓ |
v0.2.1github2026-10-21
https://github.com/6mt/dsh-control
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
v0.2.0github✓ 1 runtime-verified2026-10-20
https://github.com/6mt/dsh-control
✓dsh 0.2.1-rc.2current2026-10-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/6mt/dsh-control#v0.2.0
ID: dsh-control@v0.2.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
View checks & evidence
↳ carried from earlier record dsh-control@v0.2.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-control@v0.2.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-control@v0.2.1@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.
v0.1.1github2026-10-18
https://github.com/6mt/dsh-control
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
v0.1.0github✓ 1 runtime-verified2026-10-15
https://github.com/6mt/dsh-control
✓dsh 0.2.1-alpha.22026-10-14L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/6mt/dsh-control#v0.1.0
ID: dsh-control@v0.1.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-14 · expires: 2026-10-21
View checks & evidence
↳ carried from earlier record dsh-control@v0.2.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-control@v0.2.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-control@v0.2.1@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.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-control/)``[](https://www.dsh.so/artifact/dsh-control/)`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.
v0.2.1dsh manifestv0.2.1git2026-10-21v0.2.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (5)
- criticalsshWrite · destructive
lib/ssh.js:178command: `ssh-keygen -t ed25519 -N "" -f ~/.ssh/id_ed25519 && ssh-copy-id -i ~/.ssh/id_ed25519.pub ${target}`, - warningchildProcess · code-exec
lib/ssh.js:33child = spawn("ssh", args, { stdio: ["ignore", "pipe", "pipe"] }); - warningchildProcess · code-exec
lib/tunnel.js:99child = spawn("ssh", args, { stdio: ["ignore", "ignore", "pipe"] }); - warningnetIp · network
scripts/verify-boot-selfheal.sh:35state = {"environments": {name: {"name": name, "endpoint": "http://127.0.0.1:1", "token": "irrelevant", - warningnetIp · network
scripts/verify-install.mjs:117const base = `http://127.0.0.1:${port}`;
show 3 audit findings
- mediumRemote host key trusted on first use while harvesting the full-access launch token
lib/ssh.js:25buildProbeScript/parseTokenLine read the remote `dsh web: http://…?token=…` line (a credential that grants full control of the remote dsh) over a connection whose host key is accepted on first use. An active network MITM on that first connect can present its own key, receive the ssh session, and capture the token; the same option is used for the port forward in lib/tunnel.js:90.
- lowPasted ssh-copy-id fix command interpolates user target without quoting
lib/ssh.js:183buildAuthFix produces a shell command that the panel shows in a CopyBlock and tells the user to paste into their terminal. `target` (and `keyPath`, line 178) are interpolated unquoted, so a `user@host` value containing `;`, `$(...)` or backticks executes arbitrary local commands when pasted. Self-inflicted when the user typed the value, but it turns a shared/pasted address into terminal command injection.
- lowAny pre-existing listener on the local tunnel port is adopted and receives the remote credential
lib/tunnel.js:59If anything already listens on the chosen loopback port, TunnelManager marks it `adopted: true` without proving it is the ssh child it started. lib/connections.js then sends that endpoint the proxy `authorization` header and the `dsh-auth-*` signed cookie, and ensureCookie sends `/?token=<launch token>`, so a local process that wins the port race (or a stale/foreign listener) receives the remote dsh credential and can answer as the remote.
Static critical refuted: ssh is spawned with argv arrays, traffic goes only to user-set endpoints. Residual risks: accept-new host keys, an unquoted pasted ssh-copy-id command, silent local-port adoption.
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-21 · activity: Active
• Repo created: 2026-10-14
• Stars: ★ 0 · Forks: 0
• Health: Active — committed within last 30 days
Source
GitHub: github.com/6mt/dsh-control
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
