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 desktop client for DeepSeek Harness that launches the web UI natively, with desktop pet, themes, and token alerts.
- One-click start/stop/log management for dsh
- Transparent draggable desktop pet with bounce and sound
- Multiple themes with graphical customization editor
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 L4 · Ecosystem plugin / L5 · Ecosystem app per the three-way classification (ecosystem plugins are decided by the install step not-bundle check, so L5 does not apply; the 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.
6 samples (roughly every 7 days), 2 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-05 · 6 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-01 → 11-05 · 5 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
| plugin \ dsh | dsh 0.1.5-rc.2 | dsh 0.1.3-alpha.2 | dsh 0.1.3-alpha.1 | dsh 0.1.2-rc.1 | dsh 0.1.2-alpha.1 |
|---|---|---|---|---|---|
| v0.2.1 | ◼ | ◼ | ◼ | · | · |
v0.2.1github◼ 3 ecosystem app2026-09-12
https://github.com/dreamer0323/dsh-desktop
◼dsh 0.1.5-rc.22026-09-12Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/dreamer0323/dsh-desktop#v0.2.1
ID: dsh-desktop-75@v0.2.1@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-12 · expires: 2026-09-19
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 app
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/dreamer0323/dsh-desktop#v0.2.1
ID: dsh-desktop-75@v0.2.1@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 app
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/dreamer0323/dsh-desktop#v0.2.1
ID: dsh-desktop-75@v0.2.1@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.
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/dsh-desktop-75/?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 medium (authoritative when present) → overall medium.
v0.2.0v0.2.1git2026-11-19v0.2.1same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (11)
- warningshellExec · shell
scripts/install-dsh.mjs:56execSync(cmd, { stdio: 'ignore', shell: process.platform === 'win32' }) - warningshellExec · shell
scripts/install-dsh.mjs:83log('dsh 已安装:' + execSync('dsh --version').toString().trim()) - warningshellExec · shell
scripts/release.mjs:33execSync(cmd, { cwd: ROOT, stdio: 'inherit', ...opts }) - warningshellExec · shell
scripts/release.mjs:43execSync('curl -s -m 8 -o /dev/null https://api.github.com', { stdio: 'ignore' }) - warningshellExec · shell
scripts/release.mjs:75if (execSync('git status --porcelain', { cwd: ROOT }).toString().trim()) { - warningcurlDownload · network
scripts/release.mjs:43execSync('curl -s -m 8 -o /dev/null https://api.github.com', { stdio: 'ignore' }) - warningfsWrite · files
src/config.js:124fs.writeFileSync(file, JSON.stringify(next, null, 2) + '\n') - warningchildProcess · code-exec
src/detect.js:114? spawn('cmd.exe', ['/d', '/s', '/c', 'npm view @deepseek-ai/dsh version'], { - warningchildProcess · code-exec
src/detect.js:117: spawn('npm', ['view', '@deepseek-ai/dsh', 'version'], { stdio: 'ignore' }) - warningchildProcess · code-exec
src/server.js:133const child = spawn(spec.command, args, { - warningchildProcess · code-exec
src/server.js:201spawnSync('taskkill', ['/pid', String(child.pid), '/T', '/F'], {
show 4 audit findings
- mediumString config.command is executed through cmd.exe / /bin/sh without confirmation
src/server.js:76Any process or user able to write config.json (the userData copy, or the repo copy when running from source) gets arbitrary command execution with the user's privileges and full inherited environment at the next start/restart, with no confirmation prompt. The documented array form (config.command = ["npx", ...]) is not affected.
- mediumAuto-discovered 'harness' checkout under home is executed with the full environment
src/detect.js:66Any directory under the user's home, ~/dsh, ~/dev, ~/projects, ~/code, C:/dev or D:/dev whose name matches /harness|deepseek/i and that contains apps/cli/src/bin.ts (or a package.json whose name matches /dsh|harness/i) is selected as harnessRoot, cached into config.json, and launched as `node --import tsx/esm apps/cli/src/bin.ts web` with env {...process.env}. A repository the user merely downloaded into one of those folders therefore gains code execution and can read every secret in the shell environment (API keys, tokens).
- lowinstall-dsh.mjs interpolates the --dir argument into a shell command on Windows
scripts/install-dsh.mjs:109A --dir value containing shell metacharacters is interpreted by cmd.exe. The operator supplies this argument themselves, so the precondition is self-inflicted; an installer invoked by the desktop shell with an attacker-influenced argument would be worse.
- lowGITHUB_TOKEN interpolated into a shell command line in the release script
scripts/release.mjs:113The token is placed on a shell command line run through execSync, so it is visible in process listings/logs and any shell metacharacter in GITHUB_TOKEN would be interpreted. Dev/operator-only script, no production exposure.
Most scan warnings are benign dev-tooling/sanitised code; two real issues remain: shell-executed string config.command and auto-execution of any harness-looking checkout found under the user's home.
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-19 · activity: Inactive
• Repo created: 2026-08-17
• Stars: ★ 1 · Forks: 0
• Health: Inactive — no commit in 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 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-19 (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.
