deepseek-harness-desktop avatar

deepseek-harness-desktop

Electron desktop app for DeepSeek Harness: bundles the dsh web server and its frontend into one installable app

Ecosystem appDesktopAI ModelsNetworkWeb search
Verification
L5 · Ecosystem app
Risk
Medium
Health
Stable
Trust
Silver

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

Electron desktop app that bundles the DeepSeek Harness web server and frontend into one installable app.

  • Bundles dsh web server and frontend
  • Installable desktop application
  • Built with Electron
desktopAI

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

GitHub repository

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.

GitHub stars
0★

8 samples (roughly every 7 days), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series

09-21 → 11-05 · 8 points

Weekly star gain
+0★

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-02 → 11-05 · 7 points

Cumulative downloads
—

Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)

Only 0 points (< 3): no chart yet

no data yet

Weekly downloads
—

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

weekly board —total board —downloads ≠ unique usersstar weekly —

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

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)
◼ Ecosystem app
At-a-glance → evidence in the cards below
plugin \ dshdsh 0.1.1-rc.2
V0.1.0·
dfb0b9✗
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
V0.1.0github2026-09-11

https://github.com/xiangshangya/deepseek-harness-desktop

Ecosystem app: not installed via dsh plugin add (a desktop / web shell) — its level reads L5 · Ecosystem app.

dfb0b9github1 failed2026-09-11

https://github.com/xiangshangya/deepseek-harness-desktop

✗dsh 0.1.1-rc.22026-08-23Ecosystem app · L4 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.1-rc.2
  • • Plugin artifact: artifact unstated (historical)
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Failed
L5 runtime
Not tested
Sandbox install failed
Ecosystem app · L4 · failed

ID: deepseek-harness-desktop-21@dfb0b9@dsh0.1.1-rc.2 · profile: l4-sandbox

Issued: 2026-08-23 · expires: 2026-08-30

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-09-11
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-09-11
L4 · Install tested✕ Failed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-08-23
spec github:xiangshangya/deepseek-harness-desktop#V0.1.0 · channel GitHub source · outcome ran · exit 1
check took: 95.0s
Install succeeded✕ Failed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-08-23
spec github:xiangshangya/deepseek-harness-desktop#V0.1.0 · channel GitHub source · outcome ran · exit 1
check took: 95.0s
Installed artifact confirmed? Unknown
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-08-23
spec github:xiangshangya/deepseek-harness-desktop#V0.1.0 · channel GitHub source · outcome ran · exit 1
check took: 95.0s
L5 · Run tested– Not tested

This level was not executed in this scan.

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

Author badges

Embed the dsh.so badges in your README to show this plugin's automated security-scan and install-test status:

dsh.so risk badge
`[![dsh.so risk](https://cdn.dsh.so/badge/deepseek-harness-desktop-21.svg)](https://www.dsh.so/artifact/deepseek-harness-desktop-21/?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.

deepseek-harness-desktop-21Automated review · daily

Static low; dynamic medium (authoritative when present) → overall medium.

static low→dynamic medium→overall medium
dynamic findings0 critical·0 high·1 medium·2 low
mediumoverall · medium
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
plugin versionv0.1.4
scanned versionV0.1.4git2026-11-17
current versionV0.1.4same version
vet verdictclean · git

Vet is an AST static scan (npm artifact or git source).

show static findings (8)
  • warningchildProcess · code-execmain.js:127

    const where = spawnSync('where.exe', ['node'], { encoding: 'utf8', windowsHide: true, timeout: 15000 })

  • warningchildProcess · code-execmain.js:135

    const which = spawnSync('which', ['node'], { encoding: 'utf8', timeout: 15000 })

  • warningchildProcess · code-execmain.js:173

    const child = spawn(cmd, args, { windowsHide: true, stdio: ['ignore', 'pipe', 'pipe'] })

  • warningshellExec · shellmain.js:61

    const out = execFileSync(bin, ['--version'], { encoding: 'utf8', timeout: 15000, windowsHide: true, env: env ? { ...process.env, ...env } :

  • warningnetIp · networkmain.js:547

    log('server ready on http://127.0.0.1:' + port)

  • warningfsWrite · filesmain.js:223

    try { fs.writeFileSync(stamp, SERVER_VERSION) } catch { /* ignore */ }

  • warningfsWrite · filesmain.js:287

    logStream = fs.createWriteStream(file, { flags: 'a' })

  • warningfsWrite · filesmain.js:574

    fs.writeFileSync(shot, img.toPNG())

2model reads redacted source context · never executes plugin code
highest grademedium
merged intooverall medium
audited at2026-10-17
audited artifactgit 498fff3626e5210ea604d0c8025fbbc17957a8c1
findings0 critical·0 high1 medium / 2 low hidden
show 3 audit findings
  • mediumUpdate archive/installer is executed even when no SHA-256 digest is published, and may come from a third-party mirrormain.js:859

    Integrity verification is optional: when the release asset has no `digest` (older/uploaded-without-digest assets), downloadUpdate returns the file unchecked; applyInPlaceUpdate then unpacks it over the app's own directory with tar.exe and relaunches, and installDownloadedUpdate spawns it as an installer. The bytes are fetched from whichever source wins the speed race, which by default includes third-party mirrors (gh-proxy.com, ghfast.top, ghproxy.net) declared in updateSourceUrls, so a malicious or compromised mirror (or any TLS-terminating attacker) yields persistent code execution on the us

  • lowRelease asset fallback picks assets[0] and executes it as an installermain.js:736

    If a release contains no `-update.zip` and no `*setup*.exe`, the first asset of any type is selected, marked kind 'installer' and later spawned detached on will-quit. A mis-ordered or unrelated asset would be executed (or fail noisily) instead of being rejected, widening the blast radius of a mistaken or tampered release.

  • lowServer bearer token is written verbatim to the persistent log filemain.js:461

    The readiness line contains the one-time bearer token, and the raw stdout chunk is both echoed to the console and appended to userData/logs/dsh-server.log (only the origin is logged by the app itself). Any local process or person able to read that log can recover the token and talk to the local dsh server, which accepts plugin/command operations.

Update payload must pass a SHA-256 digest that GitHub may omit, after which it is extracted over the app or executed; other spawn/network use is expected and guarded.

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-09-27 · activity: Stable

• Repo created: 2026-08-13

• Stars: ★ 0 · Forks: 0

• Health: Stable — committed within 90 days

Source

GitHub: github.com/xiangshangya/deepseek-harness-desktop

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-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.

Was this page helpful?