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 →
What it doesAI
A cross-platform desktop launcher for DeepSeek Harness with built-in Node, embedded web UI, and auto-updates.
- Zero-dependency runtime bundles Node.js 22 LTS
- Background startup with live logs in launch page
- Auto-update via GitHub Releases and native menus
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.
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.1.5 | ◼ | ◼ | ◼ | ◼ | · |
v0.1.5github◼ 4 ecosystem app2026-09-13
https://github.com/nabin-qq273274877/dsh-desktop
◼dsh 0.1.5-rc.22026-09-13Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/nabin-qq273274877/dsh-desktop#v0.1.5
ID: dsh-desktop-102@v0.1.5@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-13 · expires: 2026-09-20
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/nabin-qq273274877/dsh-desktop#v0.1.5
ID: dsh-desktop-102@v0.1.5@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/nabin-qq273274877/dsh-desktop#v0.1.5
ID: dsh-desktop-102@v0.1.5@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.
◼dsh 0.1.2-rc.12026-09-05Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/nabin-qq273274877/dsh-desktop#v0.1.5
ID: dsh-desktop-102@v0.1.5@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
ecosystem plugin: no dsh.bundle declaration
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 official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-desktop-102/)`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 — stricter wins → overall high.
v0.3.0v0.3.0git2026-10-21v0.3.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (7)
- warningnetIp · network
src-static/main.js:73const url = event.payload || "http://127.0.0.1:3080"; - warningchildProcess · code-exec
src-tauri/src/launcher.rs:297.spawn() - warningchildProcess · code-exec
src-tauri/src/launcher.rs:304.spawn() - warningchildProcess · code-exec
src-tauri/src/launcher.rs:311.spawn() - warningnetIp · network
src-tauri/src/launcher.rs:30/// `http://127.0.0.1:3080/?token=…`. Newer DSH builds mint a fresh process - warningnetIp · network
src-tauri/src/launcher.rs:701/// fresh process token (e.g. `http://127.0.0.1:3080/?token=…`) that - warningnetIp · network
src-tauri/src/launcher.rs:726// Newer DSH prints `dsh web: http://127.0.0.1:<port>/?token=…`
show 2 audit findings
- highZip import traversal check is lexical, so '../' entries escape the DSH home and write arbitrary files
src-tauri/src/launcher.rsPath::starts_with is a purely lexical component comparison and '..' is an ordinary component, so an entry named e.g. '../../../.config/autostart/x.desktop' yields home/../../../.config/autostart/x.desktop, which still starts_with(home) == true. import_config (reachable from 运行 > 导入配置, and as the IPC command of the same name) then File::create()s that path, giving arbitrary file write as the current user (persistence via startup folders / dotfiles) whenever the victim opens a crafted .zip in the file dialog. node_modules is only skipped on export, not on import.
- lowDSH-printed URL is handed to `cmd /c start` and shell metacharacters are re-parsed by cmd.exe
src-tauri/src/launcher.rsThe URL comes from the child's stdout line `dsh web: <url>` (extract_web_url only requires an http(s) prefix and a successful Url::parse, and query '&' survives normalization). cmd.exe re-parses the raw command line, so a line like `dsh web: http://127.0.0.1:1/?t=x&calc` makes it run a second command. Not a privilege boundary in practice: the DSH child (and thus any installed plugin) already runs with the user's rights, so this is defense-in-depth only. The same pattern exists in clear_dsh_cache's restart (`sh -c "sleep 2 && \"{exe_str}\" &"` / `cmd /c timeout ... start "" &exe_str`), which on
Zip import's '..' traversal check is only lexical and bypassable, allowing arbitrary file writes; shelling the DSH-printed URL into cmd.exe is a defense-in-depth gap.
Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.
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-25 · activity: Active
• Repo created: 2026-08-31
• Stars: ★ 1 · Forks: 0
• Health: Active — committed within last 30 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).