Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.3 · 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
DSH remote access plugin using frp tunnel for mobile/external network access to web interface.
- Uses frp (frpc to your frps server) instead of Cloudflare Quick Tunnel
- Enables mobile and external network access to DSH
- Full control over speed, stability, and domain name
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-web-remote-frpInstall method: npm · runtime verified (L5) · verified on dsh 0.2.2-rc.3
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.
7 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-18 → 11-16 · 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
09-25 → 11-16 · 5 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
08-22 → 11-17 · 77 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-22 → 11-17 · 77 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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.2-rc.3 | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| 1.10.3 | ✓ | ○ | ✓ | ✗ | ✓ |
1.10.3npm✓ 17 runtime-verified1 failed2026-11-16
dsh-web-remote-frp
✓dsh 0.2.2-rc.32026-11-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: npm · dsh-web-remote-frp@1.10.3
ID: dsh-web-remote-frp@1.10.3@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-16 · expires: 2026-11-23
View checks & evidence
active in loader tree (206 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.2.2-rc.12026-11-13not tested
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · dsh-web-remote-frp@1.10.3
ID: dsh-web-remote-frp@1.10.3@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-13 · expires: 2026-11-20
View checks & evidence
inventory probe failed (rpc-error) — inconclusive, not a plugin verdict (reinterpreted 2026-11-17)
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-web-remote-frp@1.10.3
ID: dsh-web-remote-frp@1.10.3@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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-web-remote-frp@1.10.3
ID: dsh-web-remote-frp@1.10.3@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
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-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-web-remote-frp@1.10.3
ID: dsh-web-remote-frp@1.10.3@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-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.2.1-alpha.42026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-web-remote-frp@1.10.3
ID: dsh-web-remote-frp@1.10.3@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
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-web-remote-frp@1.10.3
ID: dsh-web-remote-frp@1.10.3@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-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-web-remote-frp@1.10.3
ID: dsh-web-remote-frp@1.10.3@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-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.2.0-rc.12026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-web-remote-frp@1.10.3
ID: dsh-web-remote-frp@1.10.3@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-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.1.7-rc.22026-09-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-web-remote-frp@1.10.3
ID: dsh-web-remote-frp@1.10.3@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-27 · expires: 2026-10-04
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-web-remote-frp@1.10.3
ID: dsh-web-remote-frp@1.10.3@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.7-alpha.22026-09-23L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: npm · dsh-web-remote-frp@1.10.3
ID: dsh-web-remote-frp@1.10.3@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
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-web-remote-frp@1.10.3
ID: dsh-web-remote-frp@1.10.3@dsh0.1.6-alpha.2 · profile: l3-fullscan
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-web-remote-frp@1.10.3
ID: dsh-web-remote-frp@1.10.3@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.
✓dsh 0.1.5-rc.22026-09-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: npm · dsh-web-remote-frp@1.10.3
ID: dsh-web-remote-frp@1.10.3@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-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.1.3-alpha.22026-09-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: npm · dsh-web-remote-frp@1.10.3
ID: dsh-web-remote-frp@1.10.3@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-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.
✓dsh 0.1.3-alpha.12026-09-06L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: npm · dsh-web-remote-frp@1.10.3
ID: dsh-web-remote-frp@1.10.3@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-06 · expires: 2026-09-13
View checks & evidence
active in loader tree (151 entries)
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-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: npm · dsh-web-remote-frp@1.10.3
ID: dsh-web-remote-frp@1.10.3@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-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.
✓prehistory2026-10-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-web-remote-frp@1.10.3
ID: dsh-web-remote-frp@1.10.3@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.
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-frp/?ref=badge)``[](https://www.dsh.so/artifact/dsh-web-remote-frp/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-web-remote-frp/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-web-remote-frp/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-web-remote-frp/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-web-remote-frp/?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.
v1.10.3dsh manifest1.10.3npm2026-11-191.10.3same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (9)
- warningchildProcess · code-exec
lib/index.mjs:2411tunnelHandle = subprocess.spawn(spec([frpcPath, '-c', tomlPath])); - warningshellExec · shell
lib/index.mjs:839execFileSync('tar', ['-xf', archive, '-C', tmpDir]); - warningshellExec · shell
lib/index.mjs:2813try { execFileSync('openssl', ['version'], { stdio: 'ignore' }); } - warningshellExec · shell
lib/index.mjs:2816execFileSync('openssl', [ - warningnetIp · network
lib/index.mjs:2449infoUrls: ['http://127.0.0.1:' + config.targetPort + '/frpremote/info', 'http://127.0.0.1:' + config.targetPort + '/frpremote/access'], - warningnetIp · network
lib/index.mjs:3044const url = new URL(req.url, 'http://127.0.0.1'); - warningfsWrite · files
lib/index.mjs:846if (platform !== 'win32') { try { fs.chmodSync(target, 0o755); } catch (e) { /* ignore */ } } - warningfsWrite · files
lib/index.mjs:854const file = fs.createWriteStream(dest); - warningfsWrite · files
lib/index.mjs:2393fs.writeFileSync(tomlPath, buildFrpcToml({
show 5 audit findings
- highUnauthenticated /frpremote/config lets an attacker set frpcPath (or frpDownloadUrl), which is then executed as a process
lib/index.mjsconfigHandler performs no authentication or authorization of its own, and the plugin's only access control (the proxy token) is bypassed for private/LAN sources whenever lanOpen is true (the default) — so any device on the LAN can POST {"frpcPath":"..."} or {"frpDownloadUrl":"..."}. saveIncoming writes those values into frp-config.json and immediately runs stop(); await start(); start() reads c.frpcPath verbatim and hands it to subprocess.spawn, e.g. frpcPath=/bin/sh yields ['/bin/sh','-c',tomlPath], executing the attacker-influenced TOML as a shell script (frpServerAddr='$(...)' survives JSON
- mediumfrpc binary download disables TLS certificate verification (rejectUnauthorized: false), enabling MITM binary substitution
lib/index.mjsdownloadFile accepts any TLS certificate, and the downloaded archive is unpacked (tar), chmod 0755 and executed as frpc without any hash/signature check. A network attacker (or a compromised mirror / redirect target — the code follows arbitrary Location headers) can substitute the frpc binary and obtain code execution on the host. The same routine is reachable over HTTP through /frpremote/frpc/download.
- mediumGET /frpremote/config returns all stored credentials (frp token, bot tokens, app secrets) to any reachable client
lib/index.mjseffectiveConfig() is built from CFG_KEYS, which includes frpAuthToken, tgBotToken, dingtalkAppSecret, feishuAppSecret, wecomCorpSecret and the WeChat iLink token; the handler has no auth check, and LAN clients reach it without the proxy token by default. Any LAN peer (or anyone holding the shared link token) can harvest credentials that grant control over the frps account and over every bound chat bot.
- mediumNo sender allowlist on bot channels: any chat user can obtain the DSH link+token and drive local agent sessions
lib/index.mjshandlePrivate/handleGroup, the Telegram poller, the DingTalk/Feishu/WeCom handlers and the WeChat iLink poll loop all forward messages to botRouter without checking the sender id (the id is passed but never validated), and the Feishu verification token is optional (evt.header.token is only compared when configured). Any user who can message the bound bot can therefore fetch the public URL including the access token, list sessions, read their output and inject prompts into the owner's DSH sessions — remote control of the machine's agent.
- lowHard-coded third-party mirror URLs are used to fetch and execute frpc binaries
lib/index.mjsFRP_MIRROR_URLS plus the 'https://ghfast.top/' fallback make a non-official host part of the trusted update path for an executable that is run as frpc; a compromised or hijacked mirror silently becomes a backdoor channel (compounded by the disabled TLS check and absent integrity verification).
The plugin's /frpremote/config route is unauthenticated and lets any client that reaches it (LAN clients bypass the proxy token by default) set frpcPath/frpDownloadUrl, which is then executed — host RCE.
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-08-21 · activity: Inactive
• Repo created: 2026-08-20
• Stars: ★ 0 · Forks: 2
• Health: Inactive — no commit in 90+ 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-frp?
dsh-web-remote-frp 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-frp?
Run dsh plugin --profile web add dsh-web-remote-frp 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-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.
