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
Unofficial Windows/macOS desktop app for DeepSeek Harness with bundled runtime and environment reuse.
- Cross-platform desktop app (Windows, macOS)
- Bundled runtime included
- Reuses existing DSH environments automatically
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
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 L5 · Ecosystem plugin / L5 · Ecosystem app per the three-way classification (the L1-L5 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.
11 samples (roughly every 7 days), 6 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-17 → 11-13 · 11 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
09-24 → 11-13 · 10 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◼ 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
| plugin ＼ dsh | dsh 0.1.5-rc.2 | dsh 0.1.3-alpha.2 | dsh 0.1.3-alpha.1 | dsh 0.1.2-rc.1 | dsh 0.1.2-alpha.1 |
|---|---|---|---|---|---|
| v0.5.0 | · | · | · | · | · |
v0.5.0github2026-09-11
https://github.com/yxccai/dsh-desktop
Ecosystem app: not installed via dsh plugin add (a desktop / web shell) — its level reads L5 · Ecosystem app.
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-desktop-19/?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 low (authoritative when present) → overall low.
v0.5.0v0.5.0git2026-11-14v0.5.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (12)
- warningnetIp · network
src/config.js:8url: 'http://127.0.0.1:3080', - warningfsWrite · files
src/config.js:46fs.writeFileSync(file, `${JSON.stringify(defaults, null, 2)}\n`); - warningfsWrite · files
src/dsh-integration.js:98fs.writeFileSync(temp, next, { encoding: 'utf8', mode: 0o600 }); - warningchildProcess · code-exec
src/environment-detector.js:30const child = spawn(spec.command, spec.args, { windowsHide: true, stdio: 'ignore' }); - warningshellExec · shell
src/ownership-marker.js:93const out = execFileSync('tasklist.exe', ['/FI', `PID eq ${pid}`, '/FO', 'CSV', '/NH'], { - warningshellExec · shell
src/ownership-marker.js:100const out = execFileSync('powershell.exe', - warningshellExec · shell
src/ownership-marker.js:108const out = execFileSync('ps', ['-p', String(pid), '-o', 'comm='], { encoding: 'utf8', timeout: 3000 }); - warningfsWrite · files
src/ownership-marker.js:24fs.writeFileSync(temp, `${JSON.stringify(value, null, 2)}\n`, 'utf8'); - warningfsWrite · files
src/plugin-manager.js:170fs.writeFileSync(path.join(temp, MARKER_FILE), JSON.stringify({ owner: 'dsh-desktop', id, version: plugin.version, digest: plugin.digest, in - warningfsWrite · files
src/pnpm-runtime.js:74fs.writeFileSync(temp, content, { encoding: 'utf8', mode }); - warningfsWrite · files
src/pnpm-runtime.js:100try { fs.chmodSync(path.join(dir, 'pnpm'), 0o755); } catch { /* best effort */ } - warningchildProcess · code-exec
src/runtime-manager.js:84return spawn(comspec, ['/d', '/s', '/c', line], options);
show 2 audit findings
- lowExecutable pnpm shim is written into shared $DSH_HOME/bin and given PATH precedence over system pnpm
src/pnpm-runtime.js:97The app materializes executable shim scripts in a user-configurable, easily shared directory ($DSH_HOME/bin) and prepends that directory to PATH for every spawned DSH child and for CLI children the market host spawns (DSH_MARKET_PNPM_DIR). Anything that can write $DSH_HOME/bin/pnpm (a synced/shared DSH_HOME, a co-installed tool, or a compromised plugin running in the DSH process) gains code execution with the user's privileges the next time `pnpm` is resolved; the shim is only self-healed when the bundled pnpm exists and the file content differs at launch time.
- lowOwnership-marker adoption uses loose image matching before terminating the adopted process tree
src/ownership-marker.js:163validateOwnership decides the desktop may stop (taskkill /t [/f] or SIGKILL on POSIX) the process described by a marker found in userData. The image check is a two-way substring match and the command-line check is merely `commandLine.includes(port)` (typically '3080'), so a marker whose command is a short string such as 'dsh' or 'node' plus any live process whose image name contains it and whose command line contains the port would be accepted. Exploiting this requires local write access to the marker file in userData, i.e. a position that already implies code execution as the user, hence low
No critical/high risk found: the 17 heuristic warnings are guarded child-process, filesystem and loopback-HTTP paths; only two low-severity hardening gaps remain.
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-08-21 · activity: Stable
• Repo created: 2026-08-15
• Stars: ★ 11 · Forks: 2
• Health: Stable — committed within 90 days
Source
GitHub: github.com/yxccai/dsh-desktop
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-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-14 (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.