DSH_Desktop avatar

DSH_Desktop

DeepSeek桌面版,支持Windows 10/11(x64)、macOS、Linux(x64)不同操作系统一键安装

Ecosystem appDesktopTerminal / Shell
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

Cross-platform desktop client for DeepSeek Harness, wrapping the CLI into a native window app with tray support.

  • Native window app for Windows, macOS, Linux
  • System tray, native menus, single instance
  • No Node.js required; install via GitHub Releases
desktopAIterminalAI

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
1★

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

09-17 → 11-05 · 7 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

09-24 → 11-05 · 6 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.1.0·
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
v1.1.0github2026-09-11

https://github.com/zeckauh/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-59.svg)](https://www.dsh.so/artifact/dsh-desktop-59/?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-59Automated review · daily

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

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

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

show static findings (5)
  • warningchildProcess · code-execelectron/server-manager.js:107

    const r = spawnSync('node', ['-v'], { encoding: 'utf8', timeout: 15000, windowsHide: true });

  • warningchildProcess · code-execelectron/server-manager.js:121

    ? spawnSync(process.env.ComSpec || 'cmd.exe', ['/d', '/s', '/c', 'npm config get cache'],

  • warningchildProcess · code-execelectron/server-manager.js:123

    : spawnSync('npm', ['config', 'get', 'cache'], { encoding: 'utf8', timeout: 20000 });

  • warningfsWrite · fileselectron/server-manager.js:48

    fs.appendFileSync(path.join(dataDir, 'launcher.log'), `[${new Date().toISOString()}] ${msg}\n`);

  • warningfsWrite · fileselectron/window-state.js:44

    fs.writeFileSync(this.file, JSON.stringify(this.state, null, 2));

2model reads redacted source context · never executes plugin code
highest grademedium
merged intooverall medium
audited at2026-10-19
audited artifactgit f9d6c221291093cc5f4e5aa57e7cdffc3a10dfea
findings0 critical·0 high1 medium / 3 low hidden
show 4 audit findings
  • mediumFallback launches unpinned `npx -y @deepseek-ai/dsh`, executing whatever version the registry serveselectron/server-manager.js:302

    When the bundled/cached dsh is unavailable or fails, the app silently downloads and executes the latest `@deepseek-ai/dsh` from the npm registry with full user privileges, bypassing the confirmation prompt (-y). package.json pins 0.1.0-rc.6, but this path ignores that pin, so a compromised or hijacked publish (or a registry/PATH-level npm substitution) yields code execution on every affected machine without user action.

  • lowAny local HTTP service squatting on the configured port is adopted and rendered in the privileged windowelectron/server-manager.js:317

    Readiness is decided solely by an HTTP response on `/`; the identity of the responder is never checked. A local process that binds 127.0.0.1:3080 first gets its page loaded in the app window with the `window.desktop` preload bridge (openExternal, openLogs, searchPlugins, retry) and the plugin-search script injected, enabling UI spoofing/phishing inside a trusted shell. Requires a local attacker or a hostile local service.

  • lowWindow-open and navigation handlers open any http(s) URL in the external browser without allow-listingelectron/main.js:209

    Because the DSH web UI may host third-party plugins, renderer code can trigger opening arbitrary external sites (phishing, malicious downloads) with no allow-list or user confirmation. Scheme restriction to http/https blocks the more dangerous file:/custom-scheme abuse, so impact is limited to social-engineering style links.

  • lowAuto-update downloads and installs on quit with no publisher/signature verification configuredelectron/updater.js:16

    Updates come from the GitHub `publish` provider over HTTPS and are installed on quit. package.json configures no code-signing/publisherName, so electron-updater has no trusted publisher to verify against; whoever controls the release channel (or a future publication misconfiguration) can ship code that the app installs automatically.

Electron wrapper for dsh web with solid renderer hardening, but ships an unpinned npx fetch-and-exec fallback, trusts any local service on the configured port, and auto-installs unsigned updates.

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

• Stars: ★ 1 · Forks: 0

• Health: Inactive — no commit in 90+ days

Source

GitHub: github.com/zeckauh/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?