Install verification: sandbox install ok, web smoke failed (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
Free remote access for DSH Web via Tailscale Funnel, no domain or phone app needed.
- Free Tailscale Funnel remote access
- Fixed address, no domain purchase
- Phone browser opens URL + password
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:iTrimut/dsh-WebroadInstall method: GitHub · sandbox install ok, web smoke failed (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-13 · 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-02 → 11-13 · 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
○ 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 |
|---|---|---|---|---|---|
| v1.0.1 | · | ✓ | ✓ | ✓ | ✓ |
v1.0.1github✓ 16 runtime-verified2026-11-14
https://github.com/iTrimut/dsh-Webroad
✓dsh 0.2.2-rc.12026-11-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · github:iTrimut/dsh-Webroad#v1.0.1#v1.0.1
ID: dsh-webroad@v1.0.1@dsh0.2.2-rc.1 · profile: l5-web-smoke
Issued: 2026-11-05 · expires: 2027-02-03
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: github · github:iTrimut/dsh-Webroad#v1.0.1#v1.0.1
ID: dsh-webroad@v1.0.1@dsh0.2.1-rc.5 · profile: l5-web-smoke
Issued: 2026-10-31 · expires: 2027-01-29
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 · github:iTrimut/dsh-Webroad#v1.0.1#v1.0.1
ID: dsh-webroad@v1.0.1@dsh0.2.1-rc.3 · profile: l5-web-smoke
Issued: 2026-10-26 · expires: 2027-01-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.2.1-rc.22026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · github:iTrimut/dsh-Webroad#v1.0.1#v1.0.1
ID: dsh-webroad@v1.0.1@dsh0.2.1-rc.2 · profile: l5-web-smoke
Issued: 2026-10-19 · expires: 2027-01-17
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: github · github:iTrimut/dsh-Webroad#v1.0.1#v1.0.1
ID: dsh-webroad@v1.0.1@dsh0.2.1-alpha.4 · profile: l5-web-smoke
Issued: 2026-10-16 · expires: 2027-01-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.
✓dsh 0.2.1-alpha.22026-10-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · github:iTrimut/dsh-Webroad#v1.0.1#v1.0.1
ID: dsh-webroad@v1.0.1@dsh0.2.1-alpha.2 · profile: l5-web-smoke
Issued: 2026-10-11 · expires: 2027-01-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.
✓dsh 0.2.0-rc.22026-10-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · github:iTrimut/dsh-Webroad#v1.0.1#v1.0.1
ID: dsh-webroad@v1.0.1@dsh0.2.0-rc.2 · profile: l5-web-smoke
Issued: 2026-10-08 · expires: 2027-01-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.0-rc.12026-09-29L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · github:iTrimut/dsh-Webroad#v1.0.1#v1.0.1
ID: dsh-webroad@v1.0.1@dsh0.2.0-rc.1 · profile: l5-web-smoke
Issued: 2026-09-29 · expires: 2026-12-28
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-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · github:iTrimut/dsh-Webroad#v1.0.1#v1.0.1
ID: dsh-webroad@v1.0.1@dsh0.1.7-rc.2 · profile: l5-web-smoke
Issued: 2026-09-26 · expires: 2026-12-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.1.7-alpha.22026-09-23L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · github:iTrimut/dsh-Webroad#v1.0.1#v1.0.1
ID: dsh-webroad@v1.0.1@dsh0.1.7-alpha.2 · profile: l5-web-smoke
Issued: 2026-09-23 · expires: 2026-12-22
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: github · https://github.com/iTrimut/dsh-Webroad#v1.0.1
ID: dsh-webroad@v1.0.1@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: github · github:iTrimut/dsh-Webroad#v1.0.1#v1.0.1
ID: dsh-webroad@v1.0.1@dsh0.1.6-alpha.1 · profile: l5-web-smoke
Issued: 2026-09-17 · expires: 2026-12-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.5-rc.22026-09-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · github:iTrimut/dsh-Webroad#v1.0.1#v1.0.1
ID: dsh-webroad@v1.0.1@dsh0.1.5-rc.2 · profile: l5-web-smoke
Issued: 2026-09-11 · expires: 2026-12-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.
✓dsh 0.1.3-alpha.22026-09-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · github:iTrimut/dsh-Webroad#v1.0.1#v1.0.1
ID: dsh-webroad@v1.0.1@dsh0.1.3-alpha.2 · profile: l5-web-smoke
Issued: 2026-09-08 · expires: 2026-12-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.3-alpha.12026-09-07L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · github:iTrimut/dsh-Webroad#v1.0.1#v1.0.1
ID: dsh-webroad@v1.0.1@dsh0.1.3-alpha.1 · profile: l5-web-smoke
Issued: 2026-09-07 · expires: 2026-12-06
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-05not tested
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/iTrimut/dsh-Webroad#v1.0.1
ID: dsh-webroad@v1.0.1@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-01L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · github:iTrimut/dsh-Webroad#v1.0.1#v1.0.1
ID: dsh-webroad@v1.0.1@dshunknown · profile: l5-web-smoke
Issued: 2026-10-01 · expires: 2026-12-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.
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-webroad/?ref=badge)``[](https://www.dsh.so/artifact/dsh-webroad/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-webroad/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-webroad/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-webroad/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-webroad/?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.
—94c0e7b8bd76git2026-11-1994c0e7b8bd76same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (7)
- criticalshellExec · shell
lib/tunnel.js:71execSync('cloudflared --version', { stdio: 'ignore', timeout: 5000 }); - warningnetIp · network
lib/rpc.js:24const url = new URL(req.url ?? '/', 'http://127.0.0.1'); - warningchildProcess · code-exec
lib/tunnel.js:182const child = spawn(binary.cmd, [...binary.args, ...args], { - warningshellExec · shell
lib/tunnel.js:136execFileSync('tar', ['-xzf', tarPath, '-C', destDir, '--strip-components=1'], { stdio: 'ignore' }); - warningnetIp · network
lib/tunnel.js:176: ['tunnel', '--no-autoupdate', '--url', `http://127.0.0.1:${port}`]; - warningnewFunction · code-exec
scripts/verify-scripts.mjs:11try { new Function(m[1]); console.log('PASS: panel script syntax OK'); } - warningnewFunction · code-exec
scripts/verify-scripts.mjs:24try { new Function(inner[1]); console.log('PASS: entry button script syntax OK'); }
show 3 audit findings
- highcloudflared binary is downloaded from unpinned third-party mirrors and executed without any integrity check
lib/tunnel.js:39On first public use (and whenever no local/PATH cloudflared exists) the plugin fetches an executable from GitHub 'latest' or from three third-party proxy domains (ghproxy.net, gh.ddlc.top, gh-proxy.com), unpinned by version and without any checksum or signature verification, marks it 0755 and spawns it. Whoever controls the mirror, the network path or a DNS answer can substitute the binary and obtain code execution with the plugin's privileges; the same unverified download happens automatically, so the user cannot inspect it first.
- mediumUnauthenticated loopback RPC exposes PIN, LAN-auth and tunnel control with no Origin/Host validation
lib/rpc.js:23Every request is accepted based only on the loopback bind: no token, no Origin check, no Host check, no CSRF protection. Any local process, and a web page open in the user's browser (form-encoded JSON CSRF, or DNS rebinding since the Host header is never validated), can call /pin/set, /pin/rotate, /lan/toggle, /lan/ip and /tunnel/start. That silently replaces the access PIN that guards the code-executing DSH with an attacker-known 8-digit value and can turn public exposure on; the read side (/status) returns the service state object used by the panel, which contains the current PINs.
- mediumProxy deliberately rewrites Host/Origin to loopback, disabling DSH's trust fence for all remote clients
cordis.patch.yml:14The plugin's design substitutes DSH's host-based trust control with a single 8-digit PIN: every LAN or internet client is presented to DSH as if it were a local loopback caller, so host validation, trustedHosts and any loopback-only assumptions no longer protect the instance. Any PIN disclosure or bypass (see the unauthenticated loopback RPC finding, and the unverified binary above) therefore translates directly into full access to a code-executing DSH, not merely a partially trusted session.
Loopback control RPC is unauthenticated and the plugin downloads an unverified cloudflared binary from third-party mirrors and executes it.
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-09-02 · activity: Stable
• Repo created: 2026-08-21
• Stars: ★ 1 · Forks: 0
• Health: Stable — committed within 90 days
Source
GitHub: github.com/iTrimut/dsh-Webroad
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-Webroad?
dsh-Webroad 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-Webroad?
Run dsh plugin --profile web add github:iTrimut/dsh-Webroad in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4); the web smoke test (L5) has not passed yet.
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.
