This repository has been renamed: mrRisega/dsh-remote — click to visit the new location. Everything below is preserved as originally indexed.
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. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.Install verification details →
Data as of (UTC)
What it doesAI
Secure remote control for DeepSeek Harness from any phone browser via a mobile web client and reverse proxy.
- Secure gateway with reverse proxy
- Mobile web client and PWA support
- Full feature coverage including privileged methods
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:mrgaoang/dsh-remote#v0.6.18Install method: GitHub · runtime test inconclusive (L5 unknown) · verified on dsh 0.2.0-rc.2
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.0-rc.2 | dsh 0.2.0-rc.1 | dsh 0.1.7-rc.2 | dsh 0.1.7-rc.1 | dsh 0.1.7-alpha.2 |
|---|---|---|---|---|---|
| v1.0.0 | · | ○ | ○ | · | ○ |
| v0.6.18 | ○ | · | · | · | · |
v1.0.0github○ 10 ecosystem plugin2026-10-04
https://github.com/mrgaoang/dsh-remote
○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/mrgaoang/dsh-remote#v1.0.0
ID: dsh-remote-7@v1.0.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-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.1.7-rc.22026-09-25Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/mrgaoang/dsh-remote#v1.0.0
ID: dsh-remote-7@v1.0.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
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.1.7-alpha.22026-09-23Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/mrgaoang/dsh-remote#v1.0.0
ID: dsh-remote-7@v1.0.0@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
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.1.6-alpha.22026-09-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/mrgaoang/dsh-remote#v1.0.0
ID: dsh-remote-7@v1.0.0@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
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.1.6-alpha.12026-09-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/mrgaoang/dsh-remote#v1.0.0
ID: dsh-remote-7@v1.0.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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.1.5-rc.22026-09-12Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/mrgaoang/dsh-remote#v1.0.0
ID: dsh-remote-7@v1.0.0@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-12 · expires: 2026-09-19
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.1.3-alpha.22026-09-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/mrgaoang/dsh-remote#v1.0.0
ID: dsh-remote-7@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.
○dsh 0.1.3-alpha.12026-09-07Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/mrgaoang/dsh-remote#v1.0.0
ID: dsh-remote-7@v1.0.0@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
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.1.2-rc.12026-09-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/mrgaoang/dsh-remote#v1.0.0
ID: dsh-remote-7@v1.0.0@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
ecosystem plugin: no dsh.bundle declaration
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-10-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/mrgaoang/dsh-remote#v1.0.0
ID: dsh-remote-7@v1.0.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
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.
v0.6.18github○ 1 ecosystem plugin2026-10-08
https://github.com/mrgaoang/dsh-remote
○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/mrgaoang/dsh-remote#v0.6.18
ID: dsh-remote-7@v0.6.18@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
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 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-7/?ref=badge)`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 high (authoritative when present) → overall high.
v1.0.0v1.0.0git2026-10-08v1.0.0same versionsuspicious · gitVet is an AST static scan (npm artifact or git source).
show static findings (8)
- warningnetIp · network
bin/dsh-remote.js:16DSH_REMOTE_UPSTREAM dsh web 地址(默认 http://127.0.0.1:3080) - warningnetIp · network
install.sh:49UPSTREAM="${DSH_REMOTE_UPSTREAM:-http://127.0.0.1:3080}" - warningcurlDownload · network
install.sh:81if curl -fsSL --connect-timeout 8 --max-time 60 "$url" -o /tmp/dsh-remote.tar.gz 2>/dev/null \ - warningnetIp · network
lib/config.js:15const DEFAULT_UPSTREAM = "http://127.0.0.1:3080"; - warningnetIp · network
scripts/install-macos.sh:55"upstream": "http://127.0.0.1:3080", - warningnetIp · network
scripts/install-macos.sh:81if curl -s -o /dev/null http://127.0.0.1:3443/login 2>/dev/null; then - warningnetIp · network
scripts/install-macos.sh:82echo "[install] 本机访问: http://127.0.0.1:3443/login" - warningcurlDownload · network
scripts/install-macos.sh:81if curl -s -o /dev/null http://127.0.0.1:3443/login 2>/dev/null; then
show 5 audit findings
- highUnauthenticated request with a malformed Cookie crashes the gateway process
lib/server.js:44parseCookies() has no error handling, so a request such as `GET /` with header `Cookie: a=%` makes decodeURIComponent throw a URIError inside the async request handler. The handler is registered directly on http(s).createServer() and its promise is never awaited or caught, so Node's default unhandled-rejection behaviour terminates the process. No authentication or special path is needed, the port is bound to 0.0.0.0 by default, and repeating the request keeps the gateway down even though systemd (Restart=on-failure, RestartSec=3) / launchd restarts it.
- mediumClient-controlled X-Forwarded-For defeats login rate limiting and the IP allowlist
lib/proxy.js:45clientIp() blindly trusts the client-supplied X-Forwarded-For header, and there is no trusted-proxy concept. server.js uses it as the key of LoginRateLimiter in handleLogin and for the allowIp() check. An attacker can therefore send a different X-Forwarded-For on every POST /api/login and never be blocked (default 5 attempts / 15 min becomes unlimited password guessing against the gateway's only credential, which then yields full remote control of the local dsh harness), and can spoof any address listed in DSH_REMOTE_ALLOW_IPS to bypass that secondary control. Unique values also inflate the li
- lowProxy strips Origin/Referer/Sec-Fetch-* and rewrites Host, disabling the upstream's origin fence
lib/proxy.js:19Every authenticated request is forwarded with Host set to the loopback upstream authority and with Origin/Referer/Sec-Fetch-* removed, so dsh web's local-access/origin trust fence sees a no-Origin local request. This is intentional ('loopback masquerading', as the module comment and package.json state), but it means the upstream's anti-CSRF/anti-rebinding checks never apply behind this gateway and the login password (see rate-limit bypass above) becomes the single barrier for local-equivalent control of dsh.
- lowInstaller executes an unverified tarball fetched from a third-party mirror
install.sh:77fetch_tarball() tries a third-party mirror (ghproxy.net) first, only checks that the download looks like gzip, then extracts it into the install directory and registers it as a persistent launchd/systemd service (as root when the installer is run with sudo). There is no checksum or signature verification, so the mirror operator or a network attacker can substitute code that runs with the installer's privileges on every boot.
- lowLinux systemd unit is created without User=, running the network gateway as root
install.sh:205When the installer runs as root (the branch guarded by `if [ "$(id -u)" -eq 0 ]`), the generated unit has no User=/Group= and no sandboxing, so the internet-facing gateway and everything it proxies to dsh web run with full root privileges. Any flaw in the gateway (for example the crash above) or in the upstream therefore escalates to root.
Solid scrypt/HttpOnly gateway, but a malformed Cookie crashes it unauthenticated (high) and spoofable X-Forwarded-For defeats login rate limiting and the IP allowlist.
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-14 · activity: Active
• Repo created: 2026-08-19
• Stars: ★ 63 · Forks: 13
• Health: Active — committed within last 30 days
Source
GitHub: github.com/mrgaoang/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).
Frequently asked questions
What is dsh-remote?
dsh-remote is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.
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?
Run dsh plugin --profile web add github:mrgaoang/dsh-remote#v1.0.0 in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.
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-19 (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.
