dsh-desktop avatar

dsh-desktop

Ecosystem appDesktop
Verification
L5 · Ecosystem app
Risk
Medium
Health
Stable
Trust
Silver

Install verification: Ecosystem app: not installed via dsh plugin add, so the L1-L5 plugin install-verification ladder does not apply; the security scan still runs.Install verification details →

Data as of (UTC)

What it doesAI

A thin Tauri 2 desktop shell that hosts the DeepSeek Harness Web GUI as a native app.

  • Thin host wrapper, not a fork; installs dsh web via npx
  • Single instance, system tray, close-to-tray behavior
  • Crash self-heal and graceful shutdown support
desktopAI

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

GitHub repository

Ecosystem apps are not installable via dsh plugin add: desktop / web shells install or deploy through their own release channel (GitHub Releases or the project site).

The level reads L4 · Ecosystem plugin / L5 · Ecosystem app per the three-way classification (ecosystem plugins are decided by the install step not-bundle check, so L5 does not apply; the ladder does not rate them); the security scan still runs.

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.

GitHub stars
0★

8 samples (roughly every 7 days), 2 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series

09-21 → 11-14 · 8 points

Weekly star gain
+0★

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-01 → 11-14 · 7 points

Cumulative downloads
—

Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)

Only 0 points (< 3): no chart yet

no data yet

Weekly downloads
—

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

weekly board —total board —downloads ≠ unique usersstar weekly —

Verification & Compatibility◼ Ecosystem app

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

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)
◼ Ecosystem app
At-a-glance → evidence in the cards below
plugin \ dshdsh 0.1.5-rc.2dsh 0.1.3-alpha.2dsh 0.1.3-alpha.1dsh 0.1.2-rc.1dsh 0.1.2-alpha.1
v0.1.0◼◼◼◼·
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
v0.1.0github◼ 4 ecosystem app2026-09-11

https://github.com/baikangwang/dsh-desktop

◼dsh 0.1.5-rc.22026-09-11Ecosystem app
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.5-rc.2
  • • Plugin artifact: github · https://github.com/baikangwang/dsh-desktop#v0.1.0
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Passed
L5 runtime
Unknown
Ecosystem app: not installed via `dsh plugin add` (desktop / web shell) and no install verdict was produced — it ships through its own release channel and the L1-L5 ladder does not rate it (shown as L5 · ecosystem app)
Ecosystem app

ID: dsh-desktop-81@v0.1.0@dsh0.1.5-rc.2 · profile: l4-sandbox

Issued: 2026-09-11 · expires: 2026-09-18

View checks & evidence
L1 · Found✓ Passed
L2 · Structured✓ Passed
L3 · Install spec✓ Passed
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-11
spec github:baikangwang/dsh-desktop#v0.1.0 · channel GitHub source · outcome ran · exit 0
check took: 2.4s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-11
spec github:baikangwang/dsh-desktop#v0.1.0 · channel GitHub source · outcome ran · exit 0
check took: 2.4s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-11
spec github:baikangwang/dsh-desktop#v0.1.0 · channel GitHub source · outcome ran · exit 0
check took: 2.4s
L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-11
spec github:baikangwang/dsh-desktop#v0.1.0 · install mode reused L4 scratch
check took: 54ms
Web boot ready✓ Passed
Source: DSH runtime · Method: web boot · Captured 2026-09-11
ready line dsh web: http://127.0.0.1:53173/?token=…
HTTP endpoint served✓ Passed
Source: DSH runtime · Method: HTTP request · Captured 2026-09-11
path / · HTTP 200 · took 54ms
Plugin active in inventory? Unknown
Source: DSH runtime · Method: plugin inventory query · Captured 2026-09-11
verdict not-found · entries 149
phases: active 121 · null 28
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.3-alpha.22026-09-08Ecosystem app
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.3-alpha.2
  • • Plugin artifact: github · https://github.com/baikangwang/dsh-desktop#v0.1.0
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Passed
L5 runtime
Unknown
Ecosystem app: not installed via `dsh plugin add` (desktop / web shell) and no install verdict was produced — it ships through its own release channel and the L1-L5 ladder does not rate it (shown as L5 · ecosystem app)
Ecosystem app

ID: dsh-desktop-81@v0.1.0@dsh0.1.3-alpha.2 · profile: l4-sandbox

Issued: 2026-09-08 · expires: 2026-09-15

View checks & evidence
L1 · Found✓ Passed
L2 · Structured✓ Passed
L3 · Install spec✓ Passed
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-08
spec github:baikangwang/dsh-desktop#v0.1.0 · channel GitHub source · outcome ran · exit 0
check took: 2.9s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-08
spec github:baikangwang/dsh-desktop#v0.1.0 · channel GitHub source · outcome ran · exit 0
check took: 2.9s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-08
spec github:baikangwang/dsh-desktop#v0.1.0 · channel GitHub source · outcome ran · exit 0
check took: 2.9s
L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-08
spec github:baikangwang/dsh-desktop#v0.1.0 · install mode reused L4 scratch
check took: 102ms
Web boot ready✓ Passed
Source: DSH runtime · Method: web boot · Captured 2026-09-08
ready line dsh web: http://127.0.0.1:60640/?token=…
HTTP endpoint served✓ Passed
Source: DSH runtime · Method: HTTP request · Captured 2026-09-08
path / · HTTP 200 · took 102ms
Plugin active in inventory? Unknown
Source: DSH runtime · Method: plugin inventory query · Captured 2026-09-08
verdict not-found · entries 149
phases: active 121 · null 28
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.3-alpha.12026-09-07Ecosystem app
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.3-alpha.1
  • • Plugin artifact: github · https://github.com/baikangwang/dsh-desktop#v0.1.0
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Passed
L5 runtime
Unknown
Ecosystem app: not installed via `dsh plugin add` (desktop / web shell) and no install verdict was produced — it ships through its own release channel and the L1-L5 ladder does not rate it (shown as L5 · ecosystem app)
Ecosystem app

ID: dsh-desktop-81@v0.1.0@dsh0.1.3-alpha.1 · profile: l4-sandbox

Issued: 2026-09-07 · expires: 2026-09-14

View checks & evidence
L1 · Found✓ Passed
L2 · Structured✓ Passed
L3 · Install spec✓ Passed
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-07
spec github:baikangwang/dsh-desktop#v0.1.0 · channel GitHub source · outcome ran · exit 0
check took: 2.0s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-07
spec github:baikangwang/dsh-desktop#v0.1.0 · channel GitHub source · outcome ran · exit 0
check took: 2.0s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-07
spec github:baikangwang/dsh-desktop#v0.1.0 · channel GitHub source · outcome ran · exit 0
check took: 2.0s
L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-07
spec github:baikangwang/dsh-desktop#v0.1.0 · install mode reused L4 scratch
check took: 713ms
Web boot ready✓ Passed
Source: DSH runtime · Method: web boot · Captured 2026-09-07
ready line dsh web: http://127.0.0.1:52741/?token=…
HTTP endpoint served✓ Passed
Source: DSH runtime · Method: HTTP request · Captured 2026-09-07
path / · HTTP 200 · took 713ms
Plugin active in inventory? Unknown
Source: DSH runtime · Method: plugin inventory query · Captured 2026-09-07
verdict not-found · entries 150
phases: active 122 · null 28
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.2-rc.12026-09-05Ecosystem app
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.2-rc.1
  • • Plugin artifact: github · https://github.com/baikangwang/dsh-desktop#v0.1.0
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Passed
L5 runtime
Unknown
Ecosystem app: not installed via `dsh plugin add` (desktop / web shell) and no install verdict was produced — it ships through its own release channel and the L1-L5 ladder does not rate it (shown as L5 · ecosystem app)
Ecosystem app

ID: dsh-desktop-81@v0.1.0@dsh0.1.2-rc.1 · profile: l3-fullscan

Issued: 2026-09-05 · expires: 2026-09-12

View checks & evidence
L1 · Found✓ Passed
L2 · Structured✓ Passed
L3 · Install spec✓ Passed
L4 · Install tested✓ Passed
Install succeeded✓ Passed
L5 · Run tested? Unknown

ecosystem plugin: no dsh.bundle declaration

Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-04
spec github:baikangwang/dsh-desktop#v0.1.0 · install mode reused L4 scratch
check took: 50ms
Web boot ready✓ Passed
Source: DSH runtime · Method: web boot · Captured 2026-09-04
ready line dsh web: http://127.0.0.1:51229/?token=…
HTTP endpoint served✓ Passed
Source: DSH runtime · Method: HTTP request · Captured 2026-09-04
path / · HTTP 200 · took 50ms
Plugin active in inventory? Unknown
Source: DSH runtime · Method: plugin inventory query · Captured 2026-09-04
verdict not-found · entries 149
phases: active 121 · null 28
ecosystem plugin: installed, but declares no dsh.bundle — the install step records not-bundle (shown as L4 · ecosystem plugin; L5 does not apply)

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:

dsh.so risk badge
`[![dsh.so risk](https://cdn.dsh.so/badge/dsh-desktop-81.svg)](https://www.dsh.so/artifact/dsh-desktop-81/?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.

dsh-desktop-81Automated review · daily

Static low; dynamic medium (authoritative when present) → overall medium.

static low→dynamic medium→overall medium
dynamic findings0 critical·0 high·1 medium·2 low
mediumoverall · medium
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
plugin versionv0.1.0
scanned versionv0.1.0git2026-11-19
current versionv0.1.0same version
vet verdictclean · git

Vet is an AST static scan (npm artifact or git source).

show static findings (3)
  • criticalshellExec · shellsrc-tauri/src/dsh_manager.rs:586

    /// npm exec (npx) splits arguments at spaces, and the installed resource path

  • warningnetIp · networksrc-tauri/src/process_supervisor.rs:20

    /// Matches `dsh web: http://127.0.0.1:<port>` — the single stable contract

  • warningnetIp · networksrc-tauri/src/process_supervisor.rs:53

    url: format!("http://127.0.0.1:{port}"),

2model reads redacted source context · never executes plugin code
highest grademedium
merged intooverall medium
audited at2026-10-17
audited artifactgit 1a4877b105fd1aded7a30941d700dc7769325382
findings0 critical·0 high1 medium / 2 low hidden
show 3 audit findings
  • mediumPlugin installer interpolates tarball path and cached version into a PowerShell -Command stringsrc-tauri/src/dsh_manager.rs:501

    Values are inserted inside PowerShell single-quoted strings without escaping. `tgz` is the staged copy of the file the user picked in the tray 'install plugin' dialog, and the staged name is kept verbatim; Windows filenames may contain ' and ;, so `<name>'; <payload>; '.tgz` closes the quote and executes arbitrary PowerShell as the user. `version` comes from the writable state file %LOCALAPPDATA%\DshDesktop\cache\dsh-current.json and is interpolated the same way. Exploitation needs the user to select a crafted file (or a same-user write to the data dir), and the capability gained is comparable

  • lowStartup cleanup force-kills every node process whose command line matches '@deepseek-ai/dsh@'src-tauri/src/lifecycle.rs:276

    This runs automatically on every shell start, before any user action. The second condition contradicts the doc comment above it: any node.exe invoked as `npx @deepseek-ai/dsh ...`, e.g. the web version's own npm-cache `_npx` install or a manually started server, is killed without warning, aborting in-flight agent sessions. The interpolated npx_cache path is also placed unescaped inside a single-quoted regex, so a profile path containing ' (e.g. a user name like O'Brien) breaks the command line.

  • lowOps routes bypass the /api browser-trust fence and /api/health is unauthenticateddsd-side/index.js:37

    As the file's own header explains, exact routes match before the /api prefix route and therefore skip the browser-trust fence. /api/health answers GET/HEAD with no credential, disclosing the DSH process PID, port, uptime and the absolute DSH_HOME path to any local process (and to any server-side/local agent running on the machine); a hostile web page can issue the request but cannot read the JSON because no CORS header is returned. /api/admin/shutdown correctly requires the per-boot bearer token via DSH_DESKTOP_SHUTDOWN_TOKEN and fails closed when the token is absent.

Refuted the critical flag: the shell only has one medium risk (plugin installer interpolates paths/version into a PowerShell command) plus two low-severity issues.

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-08-16

• Stars: ★ 0 · Forks: 0

• Health: Stable — committed within 90 days

Source

GitHub: github.com/baikangwang/dsh-desktop

Frequently asked questions

What is dsh-desktop?

dsh-desktop is an ecosystem app listed on dsh.so, not a DSH plugin package: it cannot be installed with dsh plugin add and ships through the project's own release channel.

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-desktop?

This is an ecosystem app, not a plugin installable via dsh plugin add: desktop / web shells install or deploy through their own release channel. The security scan still runs, but the L1-L5 plugin install ladder does not rate it.

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.

Was this page helpful?