Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
Data as of (UTC)
What it doesAI
A lightweight native macOS shell that wraps the official DeepSeek Harness with no Electron, no telemetry and no vendor gateway.
- Native macOS shell for the official DeepSeek Harness
- Tiny footprint: ~150 lines of Swift plus one bash script
- No Electron, no telemetry, no vendor gateway
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.
8 samples (roughly every 7 days), 4 of them reconstructed (hollow dots); sampled points, not a daily series
09-28 → 11-01 · 8 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-03 → 11-01 · 6 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
The snapshot’s last-week rolling window (official npm + npmmirror combined)
Only 0 points (< 3): no chart yet
no data yet
Installation
dsh plugin --profile web add github:Underwater008/deepshell#win-v0.1.2Install method: GitHub · runtime test inconclusive (L5 unknown)
Verification & Compatibility○ Ecosystem plugin
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 current | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 |
|---|---|---|---|---|---|
| win-v0.1.2 | ○ | ○ | ○ | ○ | ○ |
| 91c833 | · | · | · | · | · |
| 3fbbeb | · | · | · | · | · |
win-v0.1.2github○ 10 ecosystem plugin2026-11-05
https://github.com/Underwater008/deepshell
○dsh 0.2.2-rc.1current2026-11-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/Underwater008/deepshell#win-v0.1.2
ID: deepshell@win-v0.1.2@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
View checks & evidence
not present in web-profile loader inventory
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-31Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/Underwater008/deepshell#win-v0.1.2
ID: deepshell@win-v0.1.2@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
not present in web-profile loader inventory
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-27Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/Underwater008/deepshell#win-v0.1.2
ID: deepshell@win-v0.1.2@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
View checks & evidence
not present in web-profile loader inventory
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-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/Underwater008/deepshell#win-v0.1.2
ID: deepshell@win-v0.1.2@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
not present in web-profile loader inventory
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-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/Underwater008/deepshell#win-v0.1.2
ID: deepshell@win-v0.1.2@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
View checks & evidence
not present in web-profile loader inventory
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-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/Underwater008/deepshell#win-v0.1.2
ID: deepshell@win-v0.1.2@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
not present in web-profile loader inventory
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-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/Underwater008/deepshell#win-v0.1.2
ID: deepshell@win-v0.1.2@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
not present in web-profile loader inventory
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-29Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/Underwater008/deepshell#win-v0.1.2
ID: deepshell@win-v0.1.2@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
not present in web-profile loader inventory
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-25Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/Underwater008/deepshell#win-v0.1.2
ID: deepshell@win-v0.1.2@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-10-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/Underwater008/deepshell#win-v0.1.2
ID: deepshell@win-v0.1.2@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
91c833local2026-09-21
Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L5 · Ecosystem plugin.
3fbbebgithub○ 2 ecosystem plugin2026-09-24
https://github.com/Underwater008/deepshell
○dsh 0.1.7-rc.12026-09-24Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/Underwater008/deepshell (version unstated)
ID: deepshell@3fbbeb@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
View checks & evidence
This level was not executed in this scan.
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-21Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/Underwater008/deepshell (version unstated)
ID: deepshell@3fbbeb@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-21 · expires: 2026-09-28
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
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/deepshell/?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 medium (authoritative when present) → overall medium.
—win-v0.1.2git2026-11-05win-v0.1.2same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (10)
- warningchildProcess · code-exec
packages/dsh-phone-connect/index.js:319const child = spawn('/bin/bash', ['-c', 'sleep 2; exec /bin/launchctl kickstart -k "$1"', 'phone-connect', `gui/${uid}/${this.label}`], { - warningshellExec · shell
packages/dsh-phone-connect/index.js:102execFile( - warningnetIp · network
packages/dsh-phone-connect/index.js:186return `cloudflared tunnel --url http://127.0.0.1:${this.port}` - warningnetIp · network
packages/dsh-phone-connect/index.js:230const url = this.connection?.authenticatedUrl?.(`http://127.0.0.1:${this.port}/`) - warningfsWrite · files
packages/dsh-phone-connect/index.js:343await fs.writeFile(this.modeFile, 'local\n') - warningshellExec · shell
packages/dsh-phone-connect/lib/peers.js:18execFile(binary, args, { timeout: 15000, maxBuffer: 4 * 1024 * 1024 }, (error, stdout) => { - warningshellExec · shell
packages/dsh-phone-connect/lib/tailscale.js:16execFile(binary, args, { - warningnetIp · network
packages/dsh-phone-connect/lib/tailscale.js:40get target() { return `http://127.0.0.1:${this.port}` } - warningnetIp · network
packages/dsh-web-search-searxng/index.js:27const DEFAULT_BASE_URL = 'http://127.0.0.1:8888' - warningnetIp · network
packages/dsh-web-search-searxng/lib/client.js:217h(Field, { key: 'f1', label: 'Endpoint', value: value.baseURL || 'http://127.0.0.1:8888', overridden: user.baseURL !== undefined }),
show 3 audit findings
- mediumEnabling Remote publishes the loopback harness to the public internet via Tailscale Funnel
packages/dsh-phone-connect/lib/tailscale.js:105A single authenticated POST /api/phone-connect {mode:'tunnel'} — or, once enabled, the 30-second resume loop in apply() — turns the 127.0.0.1 harness into a publicly reachable https://<host>.ts.net service. From then on the only gate is the launch token embedded in the URL, which the same plugin also returns in GET /api/phone-connect (localUrl/phoneUrl/qrDataUrl) and writes into ~/Library/Application Support/deepshell/run/deepshell.log. Anyone who obtains that URL, log line or QR screenshot gets the full harness, and the exposure is silently re-created on every start.
- lowConfig 'label' is unvalidated and used to build a file path and launchctl arguments
packages/dsh-phone-connect/index.js:169normalizeConfig only checks that label is a non-empty string, so a label supplied through row config or the settings.yaml namespace can contain '/' or '..' and steer which plist file is stat'ed and which launchd label is passed to launchctl. The same value is passed as the quoted $1 of the spawn('/bin/bash', ['-c', ...]) restart command; the quoting prevents shell injection (expansion results are not re-parsed), but the path effect remains.
- lowvideo_qa reads a model-chosen absolute path and uploads the file to a remote endpoint
packages/dsh-video-qa-moonshot/index.js:74The tool is invoked by the model, and both 'path' and 'question' come from tool arguments. Any prompt injection that reaches the model can make the harness read a local file (any path carrying one of the listed video extensions, up to maxVideoMB, default 90 MiB) and send its contents to the configured baseURL (default https://api.moonshot.ai/v1). The extension allow-list and size cap narrow but do not remove the channel, since recordings are exactly the kind of file a user may not expect to leave the machine.
User-driven, cookie-authenticated harness plugin; its OS/network powers are mostly guarded, but enabling Remote publishes the loopback harness publicly via Tailscale Funnel.
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-22 · 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 @Underwater008/deepshell?
@Underwater008/deepshell is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
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 @Underwater008/deepshell?
Run dsh plugin --profile web add github:Underwater008/deepshell#win-v0.1.2 in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs.
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.