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 desktop wrapper for DeepSeek Harness with native notifications, smooth window control, bundled runtime, and auto-updates.
- Native Windows notifications
- Smooth window control
- Auto-updates tracking official master
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.
current (registry 2026-11-14) · 8 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-08 · 8 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-08 · 6 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
v4.0.0github2026-09-11
https://github.com/Links2008/DeepSeek-Harness-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/deepseek-harness-desktop-15/?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.
—v4.5git2026-11-14v4.5same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (8)
- warningnetIp · network
preload.js:4if (location.origin === "http://127.0.0.1:3080" && ipcRenderer.sendSync("startup:consume-entry")) { - warningchildProcess · code-exec
runtime/daemon-host.cjs:95spawnSync("taskkill", ["/F", "/T", "/PID", String(pid)], { - warningchildProcess · code-exec
runtime/daemon-host.cjs:124backend = spawn(spec.command, spec.args, { - warningfsWrite · files
runtime/daemon-host.cjs:55fs.writeFileSync(temporary, JSON.stringify(state, null, 2) + "\n", "utf8"); - warningfsWrite · files
runtime/daemon-host.cjs:66fs.writeFileSync(logPath, `[${new Date().toISOString()}] dsh daemon backend log start\n`); - warningfsWrite · files
runtime/daemon-host.cjs:79fs.appendFileSync(logPath, "\n[dsh-daemon] log size limit reached\n"); - warningfsWrite · files
runtime/plugin-recovery.cjs:43fs.writeFileSync(temporary, JSON.stringify(manifest, null, 2) + "\n", { flag: 'wx' }); - warningfsWrite · files
runtime/window-state.cjs:34fs.writeFileSync(temporary, JSON.stringify({ ...bounds, maximized: window.isMaximized() }) + '\n');
show 3 audit findings
- lowPreload exposes window-control and update-install IPC to any origin loaded in the window
preload.js:27The origin check at the top of the file only gates the CSS injection, but the bridge itself is exposed unconditionally. If the BrowserWindow ever navigates to a non-local page (external link, redirect, plugin-rendered content), that page inherits quit/close window control, diagnostics invocation and update installation - the latter can trigger a download-and-install flow without a DSH-UI confirmation.
- lowDaemon control token persisted in plaintext inside the state JSON file
runtime/daemon-host.cjs:45writeState writes the shared control token to config.statePath with default file permissions, so any local account/process that can read that file can authenticate to the daemon pipe and issue stop/query commands against the backend.
- lowBuild-time patch injects shell:true into upstream spawn/spawnSync calls
scripts/patch-upstream-windows-release.cjs:9Only reachable during Windows release builds, and the patched call sites use build-constant arguments, so no runtime exploit is demonstrated. However, with shell:true an array of arguments is re-joined through cmd.exe, so any future argument carrying spaces or metacharacters would become command injection.
Electron desktop shell for the DSH harness: all flagged spawn/exec/fs patterns are build-time scripts or token-gated local control code; only low-severity hardening gaps found.
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-10-21 · activity: Active
• Repo created: 2026-08-14
• Stars: ★ 45 · Forks: 8
• 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).
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-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.