Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.5 · 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
Exposes the DeepSeek Harness Web GUI for remote access through a Tailscale or cloudflared tunnel; early-stage release.
- Enables remote access to the DSH Web GUI
- Supports Tailscale or cloudflared as the tunnel
- Marked early-stage — README notice should be read first
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.
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); the npm pair from every snapshot.
6 samples (roughly every 7 days), 2 of them reconstructed (hollow dots); sampled points, not a daily series
09-22 → 11-03 · 6 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-01 → 11-03 · 5 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-22 → 11-03 · 40 points
The snapshot’s last-week rolling window (official npm + npmmirror combined)
09-22 → 11-04 · 41 points
Installation
dsh plugin --profile web add dsh-tailscale-accessInstall method: npm · runtime verified (L5) · verified on dsh 0.2.1-rc.5
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
Based on a single engines.dsh range (decides alone; peerDependencies is not consulted). raw ranges
>=0.1.5-rc.2
✓ Running dsh 0.2.2-rc.1 is within the declared range — install is not blocked by version.
Deciding channel: since 0.2.1-alpha.4 DSH judges by engines.dsh when declared — peerDependencies is then not consulted.
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| plugin ＼ dsh | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| 0.1.0 | ✓ | ✓ | ✓ | ✓ | ✓ |
0.1.0npm✓ 10 runtime-verified2026-11-04
dsh-tailscale-access
✓dsh 0.2.1-rc.52026-10-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · dsh-tailscale-access@0.1.0
ID: dsh-tailscale-access@0.1.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-30 · expires: 2026-11-06
View checks & evidence
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
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-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-tailscale-access@0.1.0
ID: dsh-tailscale-access@0.1.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
View checks & evidence
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
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: npm · dsh-tailscale-access@0.1.0
ID: dsh-tailscale-access@0.1.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
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-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-tailscale-access@0.1.0
ID: dsh-tailscale-access@0.1.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
View checks & evidence
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
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-tailscale-access@0.1.0
ID: dsh-tailscale-access@0.1.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
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-tailscale-access@0.1.0
ID: dsh-tailscale-access@0.1.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
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-tailscale-access@0.1.0
ID: dsh-tailscale-access@0.1.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
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-25L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-tailscale-access@0.1.0
ID: dsh-tailscale-access@0.1.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
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-tailscale-access@0.1.0
ID: dsh-tailscale-access@0.1.0@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
View checks & evidence
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
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-tailscale-access@0.1.0
ID: dsh-tailscale-access@0.1.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-tailscale-access@0.1.0@dsh0.2.2-rc.1 (l3-fullscan)
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-tailscale-access/?ref=badge)``[](https://www.dsh.so/artifact/dsh-tailscale-access/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-tailscale-access/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-tailscale-access/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-tailscale-access/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-tailscale-access/?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 medium (authoritative when present) → overall medium.
v0.1.0dsh manifest0.1.0npm2026-11-050.1.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (9)
- criticalpipeShell · shell
lib/client/client.js:634notInstalled: 'curl -fsSL https://tailscale.com/install.sh | sh', - criticalpipeShell · shell
lib/index.js:468command: 'curl -fsSL https://tailscale.com/install.sh | sh', - criticalpipeShell · shell
lib/tailscale.js:145default: return 'curl -fsSL https://tailscale.com/install.sh | sh' - warningshellExec · shell
lib/cloudflared.js:115execFile(file, args, (error) => { if (error == null) resolve(undefined); else reject(error) }) - warningnetIp · network
lib/cloudflared.js:253const target = `http://127.0.0.1:${String(port)}` - warningcurlDownload · network
lib/cloudflared.js:84return `curl -L -o ./cloudflared ${RELEASE_BASE}/${target.asset} && chmod +x ./cloudflared` - warningchildProcessImport · code-exec
lib/tailscale.js:21import { execFile } from 'node:child_process' - warningnetIp · network
lib/tailscale.js:587port !== undefined ? `${bin} serve --bg --https=443 http://127.0.0.1:${String(port)}` : `${bin} serve status`, - warningnetIp · network
lib/tailscale.js:747return ['serve', '--bg', `--https=${String(SERVE_TLS_PORT)}`, `http://127.0.0.1:${String(localPort)}`]
show 3 audit findings
- mediumcloudflared is downloaded from a mutable 'latest' URL and executed without checksum or signature verification
lib/cloudflared.js:152With the default `allowDownload: true`, starting quick mode fetches an executable from a URL that always resolves to the newest upstream release (and follows redirects) and then marks it 0755 and runs it as `cloudflared tunnel ...` with the operator's privileges. No hash or signature is checked, so a compromised release asset or a redirected mirror yields code execution in the DSH process's user context.
- mediumConfigurable `bind` can move the cookie-injecting front door off loopback, and it is writable through the settings/action API
lib/index.js:100`bind` is accepted by `normalizeField`/`setConfig`, so any caller able to reach POST /remote-access/action (a remote card, or any local process) can rebind the front door to 0.0.0.0. The front door terminates the external session and injects the harness browser cookie, and in tailscale mode it is created with `trustProxyHeaders: true` plus an identity allowlist, so a non-loopback bind puts an identity-header-trusting gate directly on the network - if proxy.js trusts forwarded Tailscale-User-* headers, a LAN client could impersonate an allowlisted tailnet identity. The header-trust behavior its
- lowAction endpoint gate is a static, non-secret header (`x-remote-access-action: 1`)
lib/client/client.js:88The only anti-CSRF signal visible in the harvested code is a fixed header value, not a token. It blocks simple cross-site form posts, but any local process (or a same-origin page) can replay it to drive config writes, kicks and restarts. Whether lib/routes.js additionally enforces a real token, Origin/loopback checks or method checks could not be verified because that file was not harvested.
Heuristic criticals are mostly intended, sandboxed behavior; residual medium risks are an unverified cloudflared auto-download and a remotely writable non-loopback bind.
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-21 · activity: Stable
• Repo created: 2026-09-20
• Stars: ★ 0 · Forks: 0
• Health: Stable — committed within 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 @why-did/dsh-tailscale-access?
@why-did/dsh-tailscale-access 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 @why-did/dsh-tailscale-access?
Run dsh plugin --profile web add dsh-tailscale-access 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-05 (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.