The original repository has been deleted or made private. This page is an archival snapshot from indexing time; the install command may no longer work.
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 app wrapper for DeepSeek Harness Web UI with one-click Windows installer.
- Electron-based desktop app
- One-click Windows installer
- Wraps DeepSeek Harness Web UI
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.
3 samples (roughly every 5 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-18 → 10-05 · 3 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
Only 2 points (< 3): no chart yet
09-23 → 10-05 · 2 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.7-rc.2 | dsh 0.1.7-rc.1 | dsh 0.1.6-alpha.2 | dsh 0.1.6-alpha.1 | dsh 0.1.5-rc.2 |
|---|---|---|---|---|---|
| v0.1.4 | ✗ | · | ✗ | ✗ | ✗ |
v0.1.4github8 failed2026-10-01
https://github.com/Muelsysel/DeepSeek-Harness-Desktop
✗dsh 0.1.7-rc.22026-09-26Ecosystem app · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/Muelsysel/DeepSeek-Harness-Desktop#v0.1.4
ID: deepseek-harness-desktop-10@v0.1.4@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.6-alpha.22026-09-20Ecosystem app · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/Muelsysel/DeepSeek-Harness-Desktop#v0.1.4
ID: deepseek-harness-desktop-10@v0.1.4@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.6-alpha.12026-09-17Ecosystem app · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/Muelsysel/DeepSeek-Harness-Desktop#v0.1.4
ID: deepseek-harness-desktop-10@v0.1.4@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.5-rc.22026-09-13Ecosystem app · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/Muelsysel/DeepSeek-Harness-Desktop#v0.1.4
ID: deepseek-harness-desktop-10@v0.1.4@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-13 · expires: 2026-09-20
View checks & evidence
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-09Ecosystem app · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/Muelsysel/DeepSeek-Harness-Desktop#v0.1.4
ID: deepseek-harness-desktop-10@v0.1.4@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-16
View checks & evidence
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 · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/Muelsysel/DeepSeek-Harness-Desktop#v0.1.4
ID: deepseek-harness-desktop-10@v0.1.4@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
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 · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/Muelsysel/DeepSeek-Harness-Desktop#v0.1.4
ID: deepseek-harness-desktop-10@v0.1.4@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-10-01Ecosystem app · L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/Muelsysel/DeepSeek-Harness-Desktop#v0.1.4
ID: deepseek-harness-desktop-10@v0.1.4@dshunknown · profile: l4-sandbox
Issued: 2026-10-01 · expires: 2026-10-08
View checks & evidence
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/deepseek-harness-desktop-10/?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.4dsh manifestv0.1.4git2026-10-07v0.1.4same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (7)
- warningchildProcess · code-exec
apps/standalone/main.cjs:162const child = spawn( - warningnetIp · network
apps/standalone/main.cjs:201if (match) resolve(`http://127.0.0.1:${match[1]}`); - warningfsWrite · files
apps/standalone/main.cjs:52fs.appendFileSync(DEBUG_LOG, `${new Date().toISOString()} ${msg}\n`); - warningfsWrite · files
desktop/main.cjs:74fs.appendFileSync(DEBUG_LOG, `${new Date().toISOString()} ${msg}\n`); - warningfsWrite · files
desktop/main.cjs:119fs.writeFileSync(SPLASH_STATUS_FILE, token, 'utf8'); - warningchildProcess · code-exec
src/desktop.ts:189child = this.#spawn( - warningchildProcess · code-exec
src/index.ts:54spawn: (command, args, options) => spawn(command, args, options),
show 3 audit findings
- mediumwill-navigate passes arbitrary URL schemes to shell.openExternal
desktop/main.cjs:276Any top-level navigation the page drives to a non-loopback target is handed to shell.openExternal without a scheme check. Unlike setWindowOpenHandler (which whitelists ^https?:), here file:, ms-msdt:, search-ms:, smb: and other registered protocol handlers reach the Windows ShellExecute path, which can launch local programs/explorer or invoke vulnerable protocol handlers if UI content (e.g. a rendered malicious link) triggers a main-frame navigation.
- mediumStandalone app has the same unvalidated shell.openExternal on navigation
apps/standalone/main.cjs:240Identical unsafe pattern in the standalone shell: any non-matching-origin navigation target is forwarded to shell.openExternal with no scheme restriction, so local protocol handlers / file launches can be triggered from page content in the packaged app.
- lowEnv-gated remote debugging port exposes Chrome DevTools Protocol
apps/standalone/main.cjsWhen DSH_DESKTOP_DEBUG_PORT is set, the app opens a DevTools/Chrome debugging endpoint that allows attached clients to evaluate JS in the renderer (and issue navigations). Default binding is loopback, but any local process could connect; it requires the operator to opt in via the environment variable.
Solid Electron sandboxing, but the will-navigate handler forwards arbitrary (non-http) URL schemes to shell.openExternal, a reachable OS-handler launch vector.
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-15 · activity: Inactive
• Repo created: 2026-08-13
• Stars: ★ 2 · Forks: 0
• Health: Inactive — no commit in 90+ 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).
Frequently asked questions
What is DeepSeek-Harness-Desktop?
DeepSeek-Harness-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 DeepSeek-Harness-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-10-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.