Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.1 · 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
Manages remote SSH tunnels for dsh, allocating ports and maintaining resilient connections.
- Remote port allocation via registry
- Resilient SSH tunnel management
- Integrates with dsh harness
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-tunnelInstall method: npm · runtime verified (L5) · verified on dsh 0.2.2-rc.1
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-12) · 6 samples (roughly every 7 days), 2 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-05 · 6 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
10-01 → 11-05 · 5 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
08-17 → 11-11 · 76 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
08-17 → 11-13 · 76 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 1 @deepseek-ai/dsh-* packages. raw ranges
^0.1.2-alpha.3 || ^0.1.7-rc.1 || ^0.2.0-rc.2 ×1
✓ Running dsh 0.2.2-rc.2 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.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 |
|---|---|---|---|---|---|
| 0.2.2 | ✓ | · | · | · | · |
| 0.2.1 | ✓ | ✓ | ✓ | ✓ | ✓ |
| 0.2.0 | · | · | · | · | · |
| 0.1.12 | · | · | · | · | · |
| 0.1.9 | · | · | · | · | · |
0.2.2npm✓ 1 runtime-verified2026-11-13
dsh-remote-tunnel
✓dsh 0.2.2-rc.12026-11-07L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · dsh-remote-tunnel@0.2.2
ID: dsh-remote-tunnel@0.2.2@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.
0.2.1npm✓ 8 runtime-verified2026-11-05
dsh-remote-tunnel
✓dsh 0.2.2-rc.12026-11-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · dsh-remote-tunnel@0.2.1
ID: dsh-remote-tunnel@0.2.1@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-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.
✓dsh 0.2.1-rc.52026-10-31L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · dsh-remote-tunnel@0.2.1
ID: dsh-remote-tunnel@0.2.1@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
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.32026-10-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-remote-tunnel@0.2.1
ID: dsh-remote-tunnel@0.2.1@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-tunnel@0.2.1
ID: dsh-remote-tunnel@0.2.1@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.
✓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-tunnel@0.2.1
ID: dsh-remote-tunnel@0.2.1@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-tunnel@0.2.1
ID: dsh-remote-tunnel@0.2.1@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-tunnel@0.2.1
ID: dsh-remote-tunnel@0.2.1@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-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-remote-tunnel@0.2.1
ID: dsh-remote-tunnel@0.2.1@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-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.
0.2.0npm✓ 1 runtime-verified2026-10-03
dsh-remote-tunnel
✓prehistory2026-10-03L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-remote-tunnel@0.2.0
ID: dsh-remote-tunnel@0.2.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-03 · expires: 2026-10-10
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.12npm✓ 6 runtime-verified2026-10-02
dsh-remote-tunnel
✓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-tunnel@0.1.12
ID: dsh-remote-tunnel@0.1.12@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.
✓dsh 0.1.7-rc.22026-09-25L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-remote-tunnel@0.1.12
ID: dsh-remote-tunnel@0.1.12@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-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.1.7-rc.12026-09-24L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · dsh-remote-tunnel@0.1.12
ID: dsh-remote-tunnel@0.1.12@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
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-tunnel@0.1.12
ID: dsh-remote-tunnel@0.1.12@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-tunnel@0.1.12
ID: dsh-remote-tunnel@0.1.12@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.
✓prehistory2026-10-02L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-remote-tunnel@0.1.12
ID: dsh-remote-tunnel@0.1.12@dshunknown · profile: l4-sandbox
Issued: 2026-10-02 · expires: 2026-10-09
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.9npm✓ 2 runtime-verified◐ 1 testing2026-09-13
dsh-remote-tunnel
✓dsh 0.1.5-rc.22026-09-13L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: npm · dsh-remote-tunnel@0.1.9
ID: dsh-remote-tunnel@0.1.9@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-13 · expires: 2026-09-20
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.3-alpha.22026-09-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: npm · dsh-remote-tunnel@0.1.9
ID: dsh-remote-tunnel@0.1.9@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-16
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.3-alpha.12026-09-07L4 · testing (install passed, runtime untested)
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: npm · dsh-remote-tunnel@0.1.9
ID: dsh-remote-tunnel@0.1.9@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
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.
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-tunnel/?ref=badge)``[](https://www.dsh.so/artifact/dsh-remote-tunnel/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-remote-tunnel/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-remote-tunnel/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-remote-tunnel/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-remote-tunnel/?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 high; dynamic medium (authoritative when present) → overall medium.
v0.2.2dsh manifest0.2.2npm2026-11-130.2.2same versionsuspicious · npmVet is an AST static scan (npm artifact or git source).
show static findings (3)
- warningpipeShell · shell
scripts/bootstrap-remote.sh:53curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash - warningshellExec · shell
src/local/ports.js:79execFile(file, args, { timeout: timeoutMs, windowsHide: true }, (error, stdout) => { - warningchildProcess · code-exec
src/ssh.js:40const child = spawn(sshCmd[0], [...sshCmd.slice(1), ...commonSshArgs(cfg, { clearForwardings }), ...sshTargetArgs(hostDef), ...args], {
show 3 audit findings
- mediumBootstrap pipes an unpinned NodeSource script into a root shell on the remote server
scripts/bootstrap-remote.sh:49When the account has passwordless sudo and no recent Node, `dsh ... bootstrap <host>` (which streams this file to `sh -s`) executes whatever the HTTPS endpoint serves as root on the remote machine, with no checksum or signature check. A compromise of the remote endpoint or of the TLS path yields root code execution on every bootstrapped server; the installed dsh itself is also unpinned (`npm install -g @deepseek-ai/dsh`).
- lowRemote-reported login name interpolated unquoted into a remote shell command
src/ssh.js:128`user` is whatever the remote host printed for `id -un`; a hostile or compromised server can return a string containing shell metacharacters and have it re-executed by the next ssh command. The injected command runs on the same remote host under the same account, so no privilege boundary is crossed, but it silently turns a read-only probe into arbitrary remote command execution during `check`/`up`. The same unquoted pattern exists for env values in execRemote (`${k}=${v}`).
- lowssh uses StrictHostKeyChecking=accept-new on every connection (TOFU)
src/ssh.js:19Unknown host keys are accepted on first contact, so a first-time MITM can proxy the session and read the remote command traffic (including the streamed bootstrap and any values passed via execRemote env). Subsequent connects are pinned to the recorded key, but the initial trust decision is silent unless the user pre-populated known_hosts.
Well-structured ssh tunnel manager; no critical/high code issues in the reviewed files, but the bootstrap pipes a remote NodeSource script into a root shell and relies on TOFU host-key checking.
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-05 · activity: Active
• Repo created: 2026-08-15
• Stars: ★ 6 · Forks: 1
• 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-tunnel?
dsh-remote-tunnel 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-tunnel?
Run dsh plugin --profile web add dsh-remote-tunnel 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-13 (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.