Electron desktop shell for the DeepSeek Harness Web GUI; first run auto-installs a portable runtime (Node + pinned deepseek-harness), with prebuilt packs, CN mirrors and zh/en UI. DeepSeek Harness 桌面版外壳:首启自动装配运行环境,支持预构建运行包与国内镜像,界面中英双语。
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
Electron desktop shell that auto-installs a portable DeepSeek Harness runtime and provides a bilingual Web GUI.
- Auto-installs portable Node and pinned deepseek-harness on first run
- Prebuilt packs and CN mirrors for easier download
- Bilingual (zh/en) interface
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 |
|---|---|---|---|
| v0.3.0 | ◼ | ◼ | · |
v0.3.0github◼ 2 ecosystem app2026-09-11
https://github.com/66-empty/DeepSeek-Harness-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/66-empty/DeepSeek-Harness-Desktop#v0.3.0
ID: deepseek-harness-desktop-56@v0.3.0@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/66-empty/DeepSeek-Harness-Desktop#v0.3.0
ID: deepseek-harness-desktop-56@v0.3.0@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.
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/deepseek-harness-desktop-56/)`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 — stricter wins → overall medium.
—v0.4.2git2026-10-21v0.4.2same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (12)
- warningchildProcess · code-exec
main.js:300const where = spawnSync('where.exe', ['node'], { encoding: 'utf8' }) - warningchildProcess · code-exec
main.js:351spawnSync('taskkill.exe', ['/PID', String(pid), '/T', '/F'], { stdio: 'ignore', timeout: 8_000 }) - warningchildProcess · code-exec
main.js:399const proc = spawn(nodePath, args, { - warningnetIp · network
main.js:578if (target.startsWith('http://127.0.0.1:') || target.startsWith('http://localhost:')) { - warningnetIp · network
main.js:1235if (url.startsWith('http://127.0.0.1:')) settleE2E(true, `page ${url.split('?')[0]}`) - warningnetIp · network
main.js:1238if (String(failedUrl).startsWith('http://127.0.0.1:')) { - warningfsWrite · files
main.js:92fs.appendFileSync(LOG_PATH, text) - warningfsWrite · files
main.js:93fs.appendFileSync(path.join(LOG_DIR, 'crashes.log'), text) - warningfsWrite · files
main.js:257fs.writeFileSync(settingsFile(), JSON.stringify(next, null, 2) + '\n') - warningchildProcess · code-exec
provision.js:117spawnSync('taskkill.exe', ['/PID', String(pid), '/T', '/F'], { stdio: 'ignore', timeout: 8_000 }) - warningchildProcess · code-exec
provision.js:334const res = spawnSync(tar, ['-xf', zipFile, '-C', destDir], { stdio: 'pipe', timeout: 10 * 60_000, encoding: 'utf8' }) - warningchildProcess · code-exec
provision.js:535const child = spawn(file, args, {
show 3 audit findings
- mediumRuntime artifacts are installed/executed without mandatory checksum verification (Node.js is never hashed)
provision.js:864The portable node.exe, the deepseek-harness source archive and the prebuilt runtime pack are downloaded (in 'cn'/auto mode the first candidate is a third-party proxy such as ghfast.top or gh-proxy.com), extracted and then executed/built locally. When the manifest does not pin a sha256 (and for Node.js always), a malicious or compromised mirror/proxy can substitute the payload, ending in code execution as the user (node.exe is run directly; `pnpm install`/`build` runs repository scripts). Cached zips at runtimeDir/.downloads are also reused without re-verification.
- mediumpack.json alias repair allows path traversal: recursive delete/write outside the staging directory
provision.js:746`a.rel` is only checked to start with 'harness/', so a value such as 'harness/../../../../Users/<user>/Documents/x' escapes `staging`. `fs.rmSync(full, {recursive:true, force:true})` then deletes an arbitrary path writable by the user, and targetAbs (fully attacker-controlled and only checked for existence) is copied to that location or junction-linked. This is reachable through ensureRuntimePack() whenever manifest.pack.url is configured, i.e. the built-in 'prebuilt runtime pack' update channel, where the archive is downloaded from the same unverified sources.
- lowBackend auth token is written in plaintext to the desktop log file
main.js:415The authenticated GUI URL, including its `?token=` secret, is appended to ~/.dsh-desktop-logs/desktop.log (and echoed to stdout) on every boot. The token grants access to the local dsh web API/RPC endpoints if the log is copied, attached to a bug report, or read by another local process that lacks the token.
Two real gaps: runtime artifacts (Node.js/harness/runtime pack) are installed and executed without mandatory checksum verification, and pack.json alias repair can delete/write outside the staging dir.
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-22 · activity: Active
• Repo created: 2026-09-04
• 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).