dsh-desktop avatar

dsh-desktop

DeepSeek Harness 简易桌面端,可供一键式启动

Ecosystem appDesktop
Verification
L5 · Ecosystem app
Risk
Medium
Health
Inactive
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

A lightweight Electron desktop wrapper that turns the dsh web UI into a standalone window with a control panel for managing skills and plugins.

  • Embeds dsh web in a lightweight Electron desktop window
  • Control panel to enable/disable skills and plugins
  • Auto-update check every 3 hours with restart
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-03 · 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-03 · 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
v1.0.5-pure·
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
v1.0.5-puregithub2026-09-11

https://github.com/xiaoyuxiaoyuqwq/dsh-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:

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

dsh-desktop-27Automated 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 versionv1.0.0
scanned versionv1.0.5-puregit2026-11-17
current versionv1.0.5-puresame version
vet verdictclean · git

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

show static findings (9)
  • warningchildProcess · code-execmain.js:139

    const ps = spawn('powershell', ['-NoProfile', '-Command', `Start-Process cmd -ArgumentList '/c','"${bat}"' -Verb RunAs -Wait`], {

  • warningchildProcess · code-execmain.js:208

    child = spawn(node, ['--expose-internals', dshBin, 'web', '--host', HOST, '--port', PORT], {

  • warningchildProcess · code-execmain.js:325

    const proc = spawn(cmd, args, { cwd: APP_DIR, env, windowsHide: true, stdio: ['ignore', 'pipe', 'pipe'] });

  • warningshellExec · shellmain.js:33

    execFile(cmd, ['--version'], { timeout: 5000 }, (err, stdout) => {

  • warningshellExec · shellmain.js:83

    execFile(

  • warningshellExec · shellmain.js:108

    execFile('taskkill', ['/pid', String(proc.pid), '/T', '/F'], () => {});

  • warningfsWrite · filesmain.js:138

    fs.writeFileSync(bat, '@echo off\r\nreg add "HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\AppModelUnlock" /v AllowDevelopmentWithoutD

  • warningfsWrite · filesmain.js:412

    try { fs.writeFileSync(disabledFile, 'disabled\n'); } catch { return false; }

  • warningfsWrite · filesmain.js:475

    fs.writeFileSync(PATCH_FILE, out.join('\n'), 'utf8');

2model reads redacted source context · never executes plugin code
highest grademedium
merged intooverall medium
audited at2026-10-17
audited artifactgit 3948601af266b7fa1544815f10acc68ff053c1cd
findings0 critical·0 high1 medium / 2 low hidden
show 3 audit findings
  • mediumIPC handler panel:set-skill passes unvalidated renderer `name` into path.join, allowing .disabled writes/unlinks outside the skills dirmain.js:408

    `path.join` does not normalise away `..`, so a renderer passing a value such as `../../../../Users/<user>/Documents/x` makes the main process create or delete a file literally named `.disabled` anywhere the user can write, outside $DSH_HOME/skills. Impact is bounded by the fixed `.disabled` filename, but it is an unsanitised filesystem write/delete primitive that crosses the renderer→main trust boundary (handler `ipcMain.handle('panel:set-skill', (_e, name, enabled) => setSkillEnabled(name, enabled))`).

  • lowpanel:set-plugin interpolates renderer-controlled `id` into cordis.patch.yml without validationmain.js:473

    The `id` argument arriving from the renderer is written straight into the profile YAML file that the dsh/cordis loader parses on the next start; a value containing newlines or YAML syntax injects extra keys/entries into that patch file, so a compromised renderer is not limited to toggling existing plugin ids. Impact is confined to the application's own profile config and only materialises after a restart.

  • lowPrivilege elevation writes a script to a predictable temp path and runs it as admin to change HKLMmain.js:139

    enableDevModeViaUac() writes `enable-dev-mode.bat` into the user temp directory and then executes it elevated via PowerShell -Verb RunAs, permanently setting AllowDevelopmentWithoutDevLicense in HKLM. The flow is disclosed to the user through two dialogs and the UAC prompt, but any same-user process able to race the temp file can get its own content executed with administrator rights, and the registry change persists after the app is closed.

Electron wrapper for `dsh web`: no RCE or exfiltration, but privileged IPC handlers trust renderer input (skill-path traversal, YAML injection) and it elevates to admin to edit HKLM.

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: ★ 0 · Forks: 0

• Health: Inactive — no commit in 90+ days

Source

GitHub: github.com/xiaoyuxiaoyuqwq/dsh-desktop

Frequently asked questions

What is dsh-desktop?

dsh-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 dsh-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?