Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
What it doesAI
Expose dsh web to the internet via encrypted public URL for remote mobile access, no LAN or NAT traversal required.
- Encrypted public URL for secure remote access
- Works from anywhere, no LAN or Wi-Fi required
- Optional self-hosted service for full control
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 @mrrisega/dsh-remoteInstall method: npm · runtime test inconclusive (L5 unknown)
Verification & Compatibility○ Ecosystem plugin
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 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 | dsh 0.2.0-rc.1 |
|---|---|---|---|---|---|
| 1.0.0 | · | · | · | · | · |
| v1.0.0 | ○ | ○ | ○ | ○ | ○ |
| 0.7.2 | ○ | · | · | · | · |
| 0.7.1 | · | ○ | · | · | · |
| 0.6.18 | · | · | ○ | ○ | ○ |
1.0.0npm2026-09-11
@mrrisega/dsh-remote
Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L5 · Ecosystem plugin.
v1.0.0github○ 9 ecosystem plugin2026-10-18
https://github.com/mrRisega/dsh-remote
○dsh 0.2.1-rc.2current2026-10-18Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/mrRisega/dsh-remote#v1.0.0
ID: dsh-remote-11@v1.0.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
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.
○dsh 0.2.1-alpha.42026-10-15Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/mrRisega/dsh-remote#v1.0.0
ID: dsh-remote-11@v1.0.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-15 · expires: 2026-10-22
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.
○dsh 0.2.1-alpha.22026-10-10Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/mrRisega/dsh-remote#v1.0.0
ID: dsh-remote-11@v1.0.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
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.
○dsh 0.2.0-rc.22026-10-08Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/mrRisega/dsh-remote#v1.0.0
ID: dsh-remote-11@v1.0.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
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.
○dsh 0.2.0-rc.12026-09-29Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/mrRisega/dsh-remote#v1.0.0
ID: dsh-remote-11@v1.0.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
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.
○dsh 0.1.7-rc.22026-09-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/mrRisega/dsh-remote#v1.0.0
ID: dsh-remote-11@v1.0.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
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.
○dsh 0.1.6-alpha.22026-09-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/mrRisega/dsh-remote#v1.0.0
ID: dsh-remote-11@v1.0.0@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
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.
○dsh 0.1.3-alpha.22026-09-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/mrRisega/dsh-remote#v1.0.0
ID: dsh-remote-11@v1.0.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-16
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-09-30Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/mrRisega/dsh-remote#v1.0.0
ID: dsh-remote-11@v1.0.0@dshunknown · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
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.
0.7.2npm○ 1 ecosystem plugin2026-10-18
@mrrisega/dsh-remote
○dsh 0.2.1-rc.2current2026-10-18Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · @mrrisega/dsh-remote@0.7.2
ID: dsh-remote-11@0.7.2@dsh0.2.1-rc.2 · profile: l5-web-smoke
Issued: 2026-10-18 · expires: 2027-01-16
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.7.1npm○ 1 ecosystem plugin2026-10-15
@mrrisega/dsh-remote
○dsh 0.2.1-alpha.42026-10-15Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · @mrrisega/dsh-remote@0.7.1
ID: dsh-remote-11@0.7.1@dsh0.2.1-alpha.4 · profile: l5-web-smoke
Issued: 2026-10-15 · expires: 2027-01-13
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.6.18npm○ 4 ecosystem plugin2026-10-10
@mrrisega/dsh-remote
○dsh 0.2.1-alpha.22026-10-10Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · @mrrisega/dsh-remote@0.6.18
ID: dsh-remote-11@0.6.18@dsh0.2.1-alpha.2 · profile: l5-web-smoke
Issued: 2026-10-10 · expires: 2027-01-08
View checks & evidence
not present in web-profile loader inventory
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-08Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · @mrrisega/dsh-remote@0.6.18
ID: dsh-remote-11@0.6.18@dsh0.2.0-rc.2 · profile: l5-web-smoke
Issued: 2026-10-08 · expires: 2027-01-06
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.2.0-rc.12026-09-29Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · @mrrisega/dsh-remote@0.6.18
ID: dsh-remote-11@0.6.18@dsh0.2.0-rc.1 · profile: l5-web-smoke
Issued: 2026-09-29 · expires: 2026-12-28
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-09-30Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · @mrrisega/dsh-remote@0.6.18
ID: dsh-remote-11@0.6.18@dshunknown · profile: l5-web-smoke
Issued: 2026-09-30 · expires: 2026-12-29
View checks & evidence
not present in web-profile loader inventory
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-remote-11/)`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 (authoritative when present) → overall medium.
v0.7.70.7.7npm2026-10-250.7.7same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (8)
- warningshellExec · shell
clients/dsh-remote/upstream-discovery.mjs:111return String(execFileSync(cmd, args, { encoding: "utf8", timeout: timeoutMs, windowsHide: true, stdio: ["ignore", "pipe", "ignore"] }) || " - warningnetIp · network
clients/dsh-remote/upstream-discovery.mjs:39export const FALLBACK_UPSTREAM = "http://127.0.0.1:3080"; - warningnetIp · network
clients/dsh-remote/upstream-discovery.mjs:85return port ? `http://127.0.0.1:${port}` : ""; - warningnetIp · network
clients/dsh-remote/upstream-discovery.mjs:438const results = await Promise.all(entries.map(async (e) => ({ ...e, ok: await probeDshWeb(`http://127.0.0.1:${e.port}`, { timeoutMs, fetchIm - warningnetIp · network
packages/dsh-remote-web/lib/fix-prompt.js:79- 两者不一致（例如实际监听 8090，而文件/默认是 3080）→ 按**实际端口**修正: 把正确地址写进 {{upstreamFilePath}}（形如 http://127.0.0.1:8090），或给守护显式设置 DSH_BRIDGE_UPSTREAM，然后重启 bri - warningnetIp · network
packages/dsh-remote-web/lib/fix-prompt.js:136const defaultUpstreamUrl = `http://127.0.0.1:${DEFAULT_UPSTREAM_PORT}`; - warningchildProcess · code-exec
packages/dsh-remote-web/lib/offline-update.mjs:52const child = spawn(process.execPath, [setup], { - warningfsWrite · files
packages/dsh-remote-web/lib/tarball-update.js:231fs.writeFileSync(p.abs, p.data);
show 5 audit findings
- mediumclientIp() trusts client-supplied X-Forwarded-For, defeating login rate limiting and IP allowlist
lib/proxy.js:45clientIp() is used as the rate-limit key (LoginRateLimiter in lib/server.js handleLogin) and for the allowIps check (allowIp(), lib/server.js:131-133). It takes the FIRST element of X-Forwarded-For, which is fully attacker-controlled: a direct client, or a client behind nginx with $proxy_add_x_forwarded_for (which prepends the client value), can send a different value per request. Result: unlimited password guessing against the gateway's only auth factor, unbounded growth of the limiter Map (an entry per spoofed IP for the whole window, memory-exhaustion DoS), and the IP allowlist can be satis
- lowProxy deliberately strips Origin/Referer/Sec-Fetch-* to defeat the upstream dsh trust fence
lib/proxy.js:19By design (see the file comment: the Host is rewritten to loopback and Origin is removed so the fence takes its "no Origin → allow" branch), every request proxied through the gateway is indistinguishable from a local request to dsh web. The upstream's origin/CSRF-style protection is therefore neutralised for all gateway traffic. Impact is bounded because the gateway requires a valid session (and the SameSite=Strict cookie blocks cross-site requests), but any credential theft or auth bypass converts directly into full control of a service that can execute commands.
- lowSession cookie loses the Secure flag and credentials travel in cleartext when TLS is not configured
lib/server.js:255config.js leaves tls=null by default and the default bind is 0.0.0.0, so the login POST password and the session cookie are sent over plain HTTP. On the intended remote/phone or public deployment this exposes the only credential to any on-path observer, who then gains full gateway access.
- lowUnauthenticated /healthz discloses upstream URL and active session count
lib/server.js:147Any unauthenticated client can read the upstream address (normally 127.0.0.1:3080, confirming the loopback target) and whether the upstream is up, plus a live session counter, which aids reconnaissance before attacking the password-protected gateway.
- lowinstall.sh downloads and executes code via the third-party ghproxy.net mirror without integrity verification
install.sh:77fetch_tarball() tries ghproxy.net before github.com and the extracted tree is later executed as a Node service; the only validation is 'file ... | grep gzip', which does not authenticate content. A compromised or malicious mirror can serve arbitrary code that the script installs and starts (and, run as root, installs as a systemd unit). The download also uses a fixed /tmp/dsh-remote.tar.gz path.
Standalone authenticated reverse-proxy gateway: crypto/auth core is sound, but spoofable X-Forwarded-For defeats the login rate-limiter; a few low-severity hardening gaps.
Rule (2026-10-24): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); without one, the static/vet fused tier applies. 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 static/vet.
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-25 · activity: Active
• Repo created: 2026-08-19
• Stars: ★ 42 · Forks: 7
• Health: Active — committed within last 30 days
Source
GitHub: github.com/mrRisega/dsh-remote
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).