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
Desktop client for DeepSeek Harness with built-in Node.js, auto setup, and zero-command-line UX for Windows.
- Built-in Node.js, no installation required
- Three-step startup animation and auto environment repair
- Custom title bar and system tray resident
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.
9 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-16 · 9 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-16 · 7 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 |
|---|---|---|---|---|---|
| 2026.08.26 | ◼ | ◼ | ◼ | · | · |
2026.08.26github◼ 3 ecosystem app2026-09-11
https://github.com/Zhanggp98/dsh-desktop
◼dsh 0.1.5-rc.22026-09-11Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/Zhanggp98/dsh-desktop#2026.08.26
ID: dsh-desktop-39@2026.08.26@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-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.1.3-alpha.22026-09-08Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/Zhanggp98/dsh-desktop#2026.08.26
ID: dsh-desktop-39@2026.08.26@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
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.3-alpha.12026-09-07Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/Zhanggp98/dsh-desktop#2026.08.26
ID: dsh-desktop-39@2026.08.26@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
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.
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-39/?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.
v0.1.1-rc.22026.08.26git2026-11-172026.08.26same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningfsWrite · files
convert-icon.js:24fs.writeFileSync(ICON_OUT, iconBuf); - warningfsWrite · files
convert-icon.js:28fs.writeFileSync(TRAY_OUT, trayBuf); - warningfsWrite · files
convert-icon.js:32fs.writeFileSync(BLUE_OUT, blueBuf); - warningfsWrite · files
electron/lib/logger.js:31fs.writeFileSync(probe, 'ok'); - warningfsWrite · files
electron/lib/logger.js:34logStream = fs.createWriteStream(logFile, { flags: 'a' });
show 3 audit findings
- mediumRenderer-exposed plugin/skill install-uninstall IPC takes caller-supplied package names and paths; handler source not audited
electron/preload.js:33The shell page can send an arbitrary path to dsh:skill-uninstall and an arbitrary package name to dsh:plugin-install. The main-process handlers live in electron/lib/managers/skills.js and plugins.js, which were not included in the harvested source, so it cannot be confirmed that the path is constrained to the DSH skills directory or that the package name is a validated npm spec. If they are not, a compromise of the shell renderer (or a future preload bridge into the DSH iframe) would allow arbitrary directory deletion or installation of an attacker-chosen npm package, i.e. code execution in th
- lowStartup auto-update check sends a request to third-party mirror registry.npmmirror.com
electron/lib/update.js:32Every launch, 4 s after startup, the app contacts a third-party npm mirror (not the vendor's own domain), disclosing the user's IP, timing and the fact that DeepSeek Harness Desktop is running. The response is only compared as a version string, so no code is executed from it, but the channel is outbound telemetry to an unrelated operator and the mirror response is trusted implicitly.
- lowIPC handlers accept messages without validating the sending frame and store an unvalidated nav page value
electron/lib/ipc.js:28Handlers such as dsh:nav-select, dsh:win-control and dsh:close-choice-respond perform no event.senderFrame check and no value validation, and executeCloseChoice acts on whatever string arrives. Today only the trusted local shell page can reach them, so the impact is limited to state confusion (wrong manager list returned by dsh:get-data, unexpected window close/quit), but it removes a defence layer if content ever gains access to the bridge.
Electron shell for DSH; the visible shell code is mostly benign, but install/uninstall IPC surfaces reachable from the renderer and 5 runtime modules (server, env, boot, wallpaper, managers) were not in the harvested source.
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-26 · activity: Stable
• Repo created: 2026-08-14
• Stars: ★ 0 · Forks: 0
• Health: Stable — committed within 90 days
Source
GitHub: github.com/Zhanggp98/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-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.
