Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
Data as of (UTC)
What it doesAI
Windows desktop shell for DeepSeek Harness with auto-deploy, tray resident, terminal dock, and plugin store.
- Windows desktop shell for DeepSeek Harness
- Auto-deploys and launches local dsh service
- Tray resident, terminal dock, plugin store
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
dsh plugin --profile web add github:llyyhh0487/desk-harness#v1.0.1Install method: GitHub · runtime test inconclusive (L5 unknown)
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.
10 samples (roughly every 7 days), 5 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 11-11 · 10 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
09-28 → 11-11 · 9 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 plugin
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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.2-rc.3 current | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| v1.0.1 | ○ | ○ | ○ | ○ | ○ |
| v1.0.0 | · | · | · | · | · |
v1.0.1github○ 14 ecosystem plugin2026-11-16
https://github.com/llyyhh0487/desk-harness
○dsh 0.2.2-rc.3current2026-11-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/llyyhh0487/desk-harness#v1.0.1
ID: desk-harness@v1.0.1@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-16 · expires: 2026-11-23
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.2.2-rc.12026-11-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/llyyhh0487/desk-harness#v1.0.1
ID: desk-harness@v1.0.1@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
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.2.1-rc.52026-10-31Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/llyyhh0487/desk-harness#v1.0.1
ID: desk-harness@v1.0.1@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
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.2.1-rc.32026-10-27Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/llyyhh0487/desk-harness#v1.0.1
ID: desk-harness@v1.0.1@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
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.2.1-rc.22026-10-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/llyyhh0487/desk-harness#v1.0.1
ID: desk-harness@v1.0.1@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
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.2.1-alpha.42026-10-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/llyyhh0487/desk-harness#v1.0.1
ID: desk-harness@v1.0.1@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
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.2.1-alpha.22026-10-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/llyyhh0487/desk-harness#v1.0.1
ID: desk-harness@v1.0.1@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-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.2.0-rc.22026-10-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/llyyhh0487/desk-harness#v1.0.1
ID: desk-harness@v1.0.1@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
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.2.0-rc.12026-09-29Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/llyyhh0487/desk-harness#v1.0.1
ID: desk-harness@v1.0.1@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
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.7-rc.22026-09-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/llyyhh0487/desk-harness#v1.0.1
ID: desk-harness@v1.0.1@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
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.7-alpha.22026-09-23Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/llyyhh0487/desk-harness#v1.0.1
ID: desk-harness@v1.0.1@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
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.6-alpha.22026-09-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/llyyhh0487/desk-harness#v1.0.1
ID: desk-harness@v1.0.1@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
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.6-alpha.12026-09-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/llyyhh0487/desk-harness#v1.0.1
ID: desk-harness@v1.0.1@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-23
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.
○prehistory2026-10-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/llyyhh0487/desk-harness#v1.0.1
ID: desk-harness@v1.0.1@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
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.
v1.0.0github○ 4 ecosystem plugin2026-09-11
https://github.com/llyyhh0487/desk-harness
○dsh 0.1.5-rc.22026-09-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/llyyhh0487/desk-harness#v1.0.0
ID: desk-harness@v1.0.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 plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/llyyhh0487/desk-harness#v1.0.0
ID: desk-harness@v1.0.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.
○dsh 0.1.3-alpha.12026-09-07Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/llyyhh0487/desk-harness#v1.0.0
ID: desk-harness@v1.0.0@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 plugin
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · github:llyyhh0487/desk-harness#v1.0.0#v1.0.0
ID: desk-harness@v1.0.0@dsh0.1.2-rc.1 · profile: l5-web-smoke
Issued: 2026-09-05 · expires: 2026-12-04
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 dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/desk-harness/?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 high (authoritative when present) → overall high.
v1.0.1v1.0.1git2026-11-17v1.0.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (12)
- warningchildProcess · code-exec
main.js:325const r = spawnSync(process.env.ComSpec || 'cmd.exe', ['/d', '/s', '/c', 'npm root -g'], { - warningchildProcess · code-exec
main.js:503const child = spawn(process.env.ComSpec || 'cmd.exe', ['/d', '/s', '/c', '"' + line + '"'], Object.assign({ windowsHide: true, windowsVerbat - warningchildProcess · code-exec
main.js:584const wr = spawnSync(process.env.ComSpec || 'cmd.exe', ['/d', '/s', '/c', 'where npx'], { - warningshellExec · shell
main.js:535execFile(nodeExe, ['--version'], { windowsHide: true, env: spawnEnv(), timeout: 20000 }, (err, stdout) => { - warningshellExec · shell
main.js:688await execFile('powershell.exe', ['-NoProfile', '-ExecutionPolicy', 'Bypass', '-Command', ps], { windowsHide: true }); - warningshellExec · shell
main.js:1253execFile('ie4uinit.exe', ['-show'], { windowsHide: true }); - warningnetIp · network
main.js:70return u.startsWith(`http://127.0.0.1:${port}/`) || u.startsWith(`http://localhost:${port}/`); - warningnetIp · network
main.js:3347setStatus('loading', '本地服务已就绪:http://127.0.0.1:' + port); - warningnetIp · network
main.js:3348currentUrl = `http://127.0.0.1:${port}/`; - warningfsWrite · files
main.js:57fs.appendFileSync(launchLogPath, '[' + new Date().toISOString() + '] ' + line + '\n'); - warningfsWrite · files
main.js:149try { fs.writeFileSync(configPath, JSON.stringify(cfg, null, 2)); } catch { /* ignore */ } - warningfsWrite · files
main.js:433fs.writeFileSync(probe, '1');
show 5 audit findings
- highstore:uninstall uses unvalidated renderer-supplied names for recursive fs.rmSync, enabling arbitrary directory deletion
main.jsThe handler has no sender check and no validation of the uninstall list. When the supplied names match no dependency key, 'targets' is empty and the raw renderer-supplied names are used as path segments: fs.rmSync(path.join(profileDir(), 'node_modules', '..')) deletes the whole DSH profile directory, and names such as '../../../../..' climb above it (path traversal) up to the user's home directory. Any content running in the main window - which loads http://127.0.0.1:<port> and executes third-party plugin client bundles - can therefore destroy arbitrary directories without any dialog.
- mediumws:add-paths copies any readable host file into the agent workspace without any origin check
main.jsThe sibling handler ws:add uses a native dialog, but ws:add-paths accepts arbitrary absolute paths from the renderer and copies them into <workspace>/files, where the DSH agent's file tools read them. Unlike term:* (isDockSender) or setup:* (isLocalFileSender), this channel performs no sender validation, so code executing in the main window (the 127.0.0.1 page that hosts third-party plugin bundles) can stage secrets such as ~/.dsh/.credentials.yaml or ~/.dsh/config.json into a directory the agent treats as user-provided input.
- mediumstore:install/store:uninstall have no origin check while plugin installs run dependency build scripts
main.jsThe store install/uninstall channels accept renderer input with no isTrustedSender check (compare ipcMain.on('store:setup-token', (e) => { if (!isTrustedSender(e)) return; ... })) and the renderer can also choose updateTo, which is appended to the install spec unvalidated. Because the profile is forced to 'dangerouslyAllowAllBuilds: true' and pnpm is wrapped with --config.dangerouslyAllowAllBuilds=true, an arbitrary owner/repo or npm package chosen by page content gets its install scripts executed with the user's privileges - turning renderer compromise into host code execution.
- lowDock origin check is a substring regex, and term:run provides unrestricted shell execution
main.jsThe check is a substring match on the sender frame URL, so any file:// URL that ends with 'dock.html' (for example file:///C:/evil/#dock.html) passes. The dock window created by ensureDockWin installs no will-navigate / setWindowOpenHandler guard (unlike mainWin), so if the dock renderer can be navigated or framed to attacker-controlled local content, term:run/term:write/term:kill yield arbitrary command execution. No reachable navigation path could be demonstrated from the harvested file, hence low severity.
- lowPort from config.json is interpolated into the cmd service launch line without validation
main.jscfg.port is read straight from the user-writable config.json with no integer/range check (only the port-submit IPC path parses an int), and the value is concatenated into a command line passed to cmd.exe /d /c at service start (npx, dsh and abs variants). A config value such as "3080 & <command>" would be executed by cmd. A local attacker able to edit config.json can already execute code, so the practical impact is limited to configuration-integrity hardening.
Privileged IPC handlers (store:uninstall, ws:add-paths, store:install) lack sender checks; store:uninstall allows path traversal that recursively deletes arbitrary directories.
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-23 · activity: Stable
• Repo created: 2026-08-16
• Stars: ★ 1 · Forks: 0
• Health: Stable — committed within 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 desk-harness?
desk-harness is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
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 desk-harness?
Run dsh plugin --profile web add github:llyyhh0487/desk-harness#v1.0.1 in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs.
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.
