The original repository has been deleted or made private. This page is an archival snapshot from indexing time; the install command may no longer work.
Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.2-rc.1 · last checked Install verification details →
Data as of (UTC)
What it doesAI
dsh environment management plugin adding desktop windows, auto-updates, platform adaptation, billing, and a workspace code editor.
- Desktop window via Rust/Tauri host
- One-click runtime update
- Workspace code 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
dsh plugin --profile web add dsh-desktop-toolsInstall method: npm · sandbox install ok, web smoke failed (L5) · verified on dsh 0.2.2-rc.1
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.
8 samples (roughly every 7 days), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-17 → 11-02 · 8 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-23 → 11-02 · 7 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
09-12 → 11-09 · 54 points
Verification & Compatibility
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.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| 0.5.3 | ✗ | ✗ | ✗ | ✗ | ✗ |
| 0.5.0 | · | · | · | · | · |
| v0.5.0 | · | · | · | · | · |
0.5.3npm11 failed2026-11-05
dsh-desktop-tools
✗dsh 0.2.2-rc.12026-11-05L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · dsh-desktop-tools@0.5.3
ID: dsh-desktop-tools-2@0.5.3@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-rc.52026-11-01L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · dsh-desktop-tools@0.5.3
ID: dsh-desktop-tools-2@0.5.3@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
View checks & evidence
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-27L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-desktop-tools@0.5.3
ID: dsh-desktop-tools-2@0.5.3@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
View checks & evidence
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-20L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-desktop-tools@0.5.3
ID: dsh-desktop-tools-2@0.5.3@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
View checks & evidence
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-11L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-desktop-tools@0.5.3
ID: dsh-desktop-tools-2@0.5.3@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
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-09L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-desktop-tools@0.5.3
ID: dsh-desktop-tools-2@0.5.3@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
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-30L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-desktop-tools@0.5.3
ID: dsh-desktop-tools-2@0.5.3@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
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-25L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-desktop-tools@0.5.3
ID: dsh-desktop-tools-2@0.5.3@dsh0.1.7-rc.2 · profile: l3-fullscan
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
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-20L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · dsh-desktop-tools@0.5.3
ID: dsh-desktop-tools-2@0.5.3@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
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-17L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · dsh-desktop-tools@0.5.3
ID: dsh-desktop-tools-2@0.5.3@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-10-04L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-desktop-tools@0.5.3
ID: dsh-desktop-tools-2@0.5.3@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.5.0npm2026-09-12
dsh-desktop-tools
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
v0.5.0github4 failed2026-09-11
https://github.com/YUEEEEY/dsh-desktop-tools
✗dsh 0.1.5-rc.22026-09-11L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/YUEEEEY/dsh-desktop-tools#v0.5.0
ID: dsh-desktop-tools-2@v0.5.0@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
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-08L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/YUEEEEY/dsh-desktop-tools#v0.5.0
ID: dsh-desktop-tools-2@v0.5.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
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-07L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/YUEEEEY/dsh-desktop-tools#v0.5.0
ID: dsh-desktop-tools-2@v0.5.0@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
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-05L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/YUEEEEY/dsh-desktop-tools#v0.5.0
ID: dsh-desktop-tools-2@v0.5.0@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
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-tools-2/?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.
v0.5.3dsh manifest0.5.3npm2026-11-090.5.3same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (10)
- warningchildProcess · code-exec
lib/bin.js:81const child = spawn(host, args, { - warningnetIp · network
lib/bin.js:70args.push("--url", `http://127.0.0.1:${port}`); - warningchildProcess · code-exec
lib/index.js:84return spawn("cmd", ["/C", cmd], opts); - warningchildProcess · code-exec
lib/index.js:85return spawn("sh", ["-c", cmd], opts); - warningchildProcess · code-exec
lib/index.js:664const child = spawn(process.execPath, [script], { - warningshellExec · shell
lib/index.js:152const out = execFileSync(NPM_BIN, ["root", "-g"], { - warningshellExec · shell
lib/index.js:197execFile(NPM_BIN, [ - warningshellExec · shell
lib/index.js:472execFile("curl.exe", [ - warningnetIp · network
lib/index.js:751? ["--url", `http://127.0.0.1:${currentPort}`] - warningnetIp · network
lib/index.js:1986const args = ["--url", `http://127.0.0.1:${port}`];
show 7 audit findings
- highHost binary fetched from GitHub Releases and executed with no checksum/signature verification
scripts/ensure-host.mjs:103ensure-host.mjs runs automatically (package.json postinstall, plugin load, and the unauthenticated POST /api/host/ensure) and fetches an asset chosen by the GitHub API response for YUEEEEY/dsh-desktop-host, then the plugin spawns it (spawn(bin, args, {detached:true})) and even auto-launches it after web start. A compromised or substituted release asset, or an overridden DSH_HOST_GITHUB_API, yields code execution on every machine that installs or loads the plugin, with no user action.
- mediumState-changing POST endpoints lack the origin check used by the file API
lib/index.js:1977/api/runtime, /api/patches, /api/desktop and /api/host/ensure accept POSTs with no Origin/Host validation and need no body/preflight. Any web page the user visits while dsh web is running can trigger a global `npm install -g @deepseek-ai/dsh@latest`, re-apply the runtime file patches, spawn the desktop host, or start a host binary download.
- mediumPlugin rewrites code of the installed dsh runtime inside node_modules on load
lib/index.js:378On win32 (autoApplyPatches defaults true) the plugin injects a ~40-line WindowsProcessInspector class into @deepseek-ai/dsh-subprocess-local/lib/index.js and rewrites the minimal agent preset YAML, i.e. it permanently modifies another installed package that the dsh runtime then executes. The same rewrite is re-triggerable through the unauthenticated POST /api/patches. Silent self-modification of a dependency is indistinguishable from a supply-chain implant and is not reversible from the panel.
- mediumOrigin check compares Origin to Host only, and the workspace root can be repointed to any directory
lib/index.js:1068Origin==Host is satisfied under DNS rebinding, so a page on an attacker-controlled hostname that later resolves to 127.0.0.1 passes the check, can POST /api/fs/root with {dir:"/"}, and then use /api/fs/write to place arbitrary content anywhere on the filesystem (e.g. shell/startup dotfiles) and /api/fs/read to exfiltrate files. /api/fs/tree and /api/fs/read additionally have no origin check at all.
- mediumEditor page loads Monaco from third-party CDNs on the same origin as the file-write API
lib/index.js:1500/editor is served from the dsh web origin and dynamically injects script tags from registry.npmmirror.com then cdn.jsdelivr.net. Script from a compromised or hijacked CDN executes same-origin with the plugin's API and therefore passes sameOrigin(), allowing it to read and overwrite workspace files via /api/fs/read and /api/fs/write without any user interaction.
- lowDeepSeek API key read from disk is passed as a curl command-line argument
lib/index.js:526The credential is exposed in the process argument list, visible to other local users/processes. It is only sent to api.deepseek.com, and the key itself is never returned by the routes, but GET /api/billing (no origin check, no auth) exposes account balance and token usage to any local caller or web page.
- lowPath confinement in resolveInRoot checks the literal path only, so symlinks escape the workspace root
lib/index.js:858A symlink that already exists inside the workspace root (or is placed there by any tool/agent) lets /api/fs/read and /api/fs/write operate on targets outside editorRoot, defeating the documented restriction '路径严格限制在工作区根目录内'. Exploitation requires such a link to exist, so impact is bounded.
Auto-downloads and executes an unverified host binary, silently rewrites the installed dsh runtime in node_modules, and exposes unauthenticated state-changing HTTP routes.
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-21 · activity: Inactive
• Repo created: 2026-08-18
• 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-tools?
dsh-desktop-tools is a DeepSeek Harness (dsh) plugin listed on dsh.so — an independent community registry that indexes public source repositories and publishes automated security-scan and install-verification results for each entry.
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-tools?
Run dsh plugin --profile web add dsh-desktop-tools in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4); the web smoke test (L5) has not passed yet.
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-09 (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.
