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
Desktop wrapper for DeepSeek Harness using WebView2, with multi-session detached windows, system tray, and MSI installer.
- WebView2-based desktop app
- Multi-session detached windows
- System tray and adaptive MSI installer
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 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.
current (registry 2026-11-16) · 11 samples (roughly every 7 days), 5 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-15 · 11 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-15 · 10 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 |
|---|---|---|---|---|---|
| v1.1.0 | ◼ | ◼ | ◼ | ◼ | · |
v1.1.0github◼ 4 ecosystem app2026-09-11
https://github.com/cuteG41cute/dsh-desktop
◼dsh 0.1.5-rc.22026-09-11Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/cuteG41cute/dsh-desktop#v1.1.0
ID: dsh-desktop-46@v1.1.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-09Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/cuteG41cute/dsh-desktop#v1.1.0
ID: dsh-desktop-46@v1.1.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-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.1.3-alpha.12026-09-07Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/cuteG41cute/dsh-desktop#v1.1.0
ID: dsh-desktop-46@v1.1.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 app
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · github:cuteG41cute/dsh-desktop#v1.1.0#v1.1.0
ID: dsh-desktop-46@v1.1.0@dsh0.1.2-rc.1 · profile: l4-sandbox
Issued: 2026-09-05 · expires: 2026-09-12
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/dsh-desktop-46/?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.
—v1.2.8git2026-11-01v3.1.2version moved onclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (12)
- warningnetIp · network
dsh-desktop/linux/dsh-desktop.py:8默认地址 http://127.0.0.1:3080(可用环境变量 DSH_WEB_URL 覆盖) - warningnetIp · network
dsh-desktop/linux/dsh-desktop.py:25BASE_URL = os.environ.get('DSH_WEB_URL', 'http://127.0.0.1:3080') - warningeval · code-exec
dsh-desktop/tools/preview-probe/attach.mjs:21async eval(expression) { - warningnetIp · network
dsh-desktop/tools/preview-probe/attach.mjs:74const list = await (await fetch(`http://127.0.0.1:${PORT}/json/list`)).json(); - warningeval · code-exec
dsh-desktop/tools/preview-probe/drive.mjs:41async eval(expression) { - warningnetIp · network
dsh-desktop/tools/preview-probe/drive.mjs:112for (let i = 0; i < 40; i++) { try { list = await (await fetch(`http://127.0.0.1:${PORT}/json/list`)).json(); if (list.some((t) => t.type == - warningnetIp · network
dsh-desktop/tools/preview-probe/drive.mjs:117await cdp.send('Page.navigate', { url: 'http://127.0.0.1:3080/' }); - warningeval · code-exec
dsh-desktop/tools/preview-probe/eval.mjs:41async eval(expression) { - warningnetIp · network
dsh-desktop/tools/preview-probe/eval.mjs:16const APP = 'http://127.0.0.1:3080'; - warningnetIp · network
dsh-desktop/tools/preview-probe/eval.mjs:58for (let i = 0; i < 40; i++) { try { list = await (await fetch(`http://127.0.0.1:${PORT}/json/list`)).json(); if (list.some((t) => t.type == - warningeval · code-exec
dsh-desktop/tools/preview-probe/verify-scope.mjs:46async eval(expression) { - warningnetIp · network
dsh-desktop/tools/preview-probe/verify-scope.mjs:247for (let i = 0; i < 40; i++) { try { list = await (await fetch(`http://127.0.0.1:${PORT}/json/list`)).json(); if (list.some((t) => t.type ==
show 5 audit findings
- mediumDev probe scripts read ~/.dsh/.credentials.yaml and forge an authenticated session cookie
dsh-desktop/tools/preview-probe/drive.mjs:21drive.mjs, eval.mjs and verify-scope.mjs each read the user's DSH credential secret and HMAC-sign a valid dsh-auth-* cookie for 127.0.0.1:3080, then install it into a headless browser they spawn. Nothing is exfiltrated today, but the package ships a reusable credential-signing primitive in files that also honour DSH_HOME/--port/--eval inputs; any later edit (or a rug-pull) in these files yields a working session token.
- mediumfile_history restore writes entry.originalPath taken from untrusted on-disk backup sidecars
backup/dsh-file-history/lib/index.jsEntries are built by readBackupRoot/readLegacyEntries from *.json sidecars under <project>/.dsh-backup/_dsh-file-history/ without checking that originalPath stays inside the project or that the sidecar was produced by this plugin (the dir is only auto-added to .gitignore). A cloned/opened repo containing a crafted .dsh-backup therefore turns file_history(action=restore/revert_turn) into an arbitrary-file-write primitive: attacker-chosen content can be written to any user-writable path (e.g. ~/.ssh/authorized_keys, shell rc) if a prompt-injected workspace convinces the model to restore it.
- lowDesktop shell injects the DSH session cookie into whatever origin the launched URL serves
dsh-desktop/linux/dsh-desktop.py:202BASE_URL comes from argv[1]/DSH_WEB_URL and the injected script executes document.cookie = <DSH_DESKTOP_AUTH_COOKIE> whenever the loaded page's innerText merely contains 'dsh web authentication required'. A hostile page (user launches dsh-desktop.py with an attacker URL) can satisfy that marker, receive the cookie in JS-writable (non-HttpOnly) form and exfiltrate it; the token is only usable against 127.0.0.1:3080, which bounds the impact.
- lowWebView enables developer extras (remote inspector) unconditionally
dsh-desktop/linux/dsh-desktop.py:152The inspector is always on in the window that also holds the session cookie and injects a userscript into all frames; it enlarges the attack surface of any hostile page loaded in the shell, although it is not remotely reachable by default.
- lowClient RPC route /dsh-file-history/api performs no authentication of its own
backup/dsh-file-history/lib/index.jsThe handler only checks the HTTP method and then dispatches set-enabled/reset-project (which mutate the backup switch) and state reads whose sessionId comes from the request body; it relies entirely on the host server's global auth. SameSite=Strict session cookies limit browser-based CSRF, so this is a hardening gap rather than a demonstrated exploit, but any caller that reaches the port can silently disable the pre-write backup safety net and read backup paths/file names.
Runtime halves look safe; medium risks: dev probes forge session cookies from ~/.dsh credentials, and file_history restore trusts on-disk backup metadata.
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-11-13 · activity: Active
• Repo created: 2026-08-15
• Stars: ★ 1 · Forks: 0
• Health: Active — committed within last 30 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-16 (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.
