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
Remote access plugin using Cloudflare Tunnel with token auth, gzip, LAN HTTPS, mobile panel, and QQ bot link retrieval.
- Cloudflare Quick Tunnel public access
- Token-based authentication for security
- Mobile panel and QQ bot integration
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:godchen520/dsh-web-remote#v5.7.7Install method: GitHub · 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-15) · 7 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-03 · 7 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-06 → 11-03 · 5 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
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
Only 0 points (< 3): no chart yet
no data yet
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.2-rc.1 | dsh 0.2.2-alpha.2 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| v5.7.9 | · | · | · | · | · |
| v5.7.7 | ✓ | ✓ | · | · | · |
| v5.7.6 | · | · | ✓ | ✓ | · |
| v5.7.5 | · | · | · | · | · |
| v5.7.3 | · | · | · | · | · |
v5.7.9github2026-11-14
https://github.com/godchen520/dsh-web-remote
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
v5.7.7github✓ 2 runtime-verified2026-11-04
https://github.com/godchen520/dsh-web-remote
✓dsh 0.2.2-rc.12026-11-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/godchen520/dsh-web-remote#v5.7.7
ID: dsh-web-remote@v5.7.7@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-04 · expires: 2026-11-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.
✓dsh 0.2.2-alpha.22026-11-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-alpha.2
- • Plugin artifact: github · https://github.com/godchen520/dsh-web-remote#v5.7.7
ID: dsh-web-remote@v5.7.7@dsh0.2.2-alpha.2 · profile: l4-sandbox
Issued: 2026-11-04 · expires: 2026-11-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.
v5.7.6github✓ 2 runtime-verified2026-10-30
https://github.com/godchen520/dsh-web-remote
✓dsh 0.2.1-rc.52026-10-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/godchen520/dsh-web-remote#v5.7.6
ID: dsh-web-remote@v5.7.6@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-30 · expires: 2026-11-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.2.1-rc.32026-10-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/godchen520/dsh-web-remote#v5.7.6
ID: dsh-web-remote@v5.7.6@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.
v5.7.5github2026-10-22
https://github.com/godchen520/dsh-web-remote
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
v5.7.3github2026-10-21
https://github.com/godchen520/dsh-web-remote
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
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-web-remote/?ref=badge)``[](https://www.dsh.so/artifact/dsh-web-remote/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-web-remote/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-web-remote/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-web-remote/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-web-remote/?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 low; dynamic high (authoritative when present) → overall high.
v5.7.9dsh manifestv5.7.9git2026-11-14v5.7.9same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (9)
- warningchildProcessImport · code-exec
lib/download.mjs:6import { execFileSync } from 'node:child_process'; - warningfsWrite · files
lib/download.mjs:35try { fs.chmodSync(tmp, 0o755); } catch (e) { /* ignore */ } - warningfsWrite · files
lib/download.mjs:43const file = fs.createWriteStream(dest); - warningnetIp · network
lib/index.mjs:181const url = connCtx.connection.authenticatedUrl('http://127.0.0.1:' + config.targetPort); - warningnetIp · network
lib/index.mjs:371const tunnelArgs = [cloudflaredPath, 'tunnel', '--url', 'http://127.0.0.1:' + httpPort, '--no-autoupdate', '--ha-connections', '4']; - warningnetIp · network
lib/index.mjs:602let telegramProxyUrl = 'http://127.0.0.1:7897'; // HTTP 代理（国内访问 api.telegram.org 必需） - warningfsWrite · files
lib/index.mjs:228fs.appendFileSync(file, new Date().toISOString() + ' [' + level + '] ' + text + '\n'); - warningnetIp · network
lib/panel.mjs:1813tProxy.value = 'http://127.0.0.1:7897'; - warningfsWrite · files
lib/store.mjs:27fs.writeFileSync(file, JSON.stringify(cache, null, 2), 'utf-8');
show 3 audit findings
- highcloudflared binary is downloaded with TLS verification disabled and executed without any integrity check
lib/download.mjs:44TLS certificate validation is disabled for the download, the 3xx branch follows Location to any host, and there is no checksum/signature check. downloadCloudflared() then does fs.chmodSync(tmp, 0o755) (line 35) and start() spawns that file via subprocess.spawn, so a network attacker (hostile Wi-Fi, transparent proxy, DNS/redirect hijack of github.com) can substitute an arbitrary binary that the plugin runs as the DSH user. Reachable by default: autoStart is true and the download runs whenever cloudflared is not found on PATH. The same helper is reused in downloadQQImageAttachments() to fetch a
- mediumlanOpen defaults to true, giving any LAN peer token-free access to the DSH agent
lib/index.mjs:117With autoStart also defaulting to true, the reverse proxy starts on plugin load and, per the documented design (header line 18: 'lanOpen 局域网免 token 默认 true（私网来源放行）'), requests from private source addresses skip the access token, while the plugin advertises LAN URLs (lanIPs()) as the primary access path. Anyone sharing the network (café/office/hotel Wi-Fi) therefore reaches the DSH UI unauthenticated, i.e. an agent that can run shell commands. The actual bypass is implemented in lib/proxy.mjs (not harvested). Note also that the cloudflared tunnel connects to the proxy from 127.0.0.1, so if the
- lowPanel routes return and rotate the proxy access token with no handler-level authentication
lib/index.mjsGET /remote/token and /remote/info (routes /remote/info, /remote/access) hand back the full proxy access token in JSON, and POST /remote/token/set can overwrite it (store.save({ webRemote: { token: next } })). Neither handler performs any authentication; they rely entirely on the host webServer protecting them. Those same paths are also reachable through the plugin's own reverse proxy, which in the default LAN mode is token-free, so a LAN visitor can read the token or rotate it and lock the legitimate user out (and the token also travels in URLs as ?token=).
Auto-downloads the cloudflared binary with TLS verification disabled and executes it unsigned; LAN access is token-free by default and panel routes leak the access token.
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: ★ 22 · Forks: 6
• 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-web-remote?
dsh-web-remote 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-web-remote?
Run dsh plugin --profile web add github:godchen520/dsh-web-remote#v5.7.9 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-15 (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.