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
Turns the DSH WebUI into a desktop window for double-click launch without a browser.
- Turns DSH WebUI into a desktop window
- Double-click launch, no browser needed
- Close window to exit, build once use forever
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.
10 samples (roughly every 7 days), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-18 → 11-16 · 10 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-02 → 11-16 · 9 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 |
|---|---|---|---|---|---|
| dcf096 | · | · | · | · | · |
| b0f1be | · | · | · | ◼ | · |
| 77c677 | ◼ | ◼ | ◼ | · | ◼ |
dcf096github2026-08-28
https://github.com/hxwi1/dsh-desktop-window
Ecosystem app: not installed via dsh plugin add (a desktop / web shell) — its level reads L5 · Ecosystem app.
b0f1begithub◼ 1 ecosystem app2026-09-04
github:hxwi1/dsh-desktop-window
◼dsh 0.1.2-rc.12026-09-04Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · github:hxwi1/dsh-desktop-window#b0f1be
ID: dsh-desktop-window-2@b0f1be@dsh0.1.2-rc.1 · profile: l5-web-smoke
Issued: 2026-09-04 · expires: 2026-12-03
View checks & evidence
L1-L3 backfilled from dsh-desktop-window-2@dcf096…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-desktop-window-2@dcf096…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-desktop-window-2@dcf096…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
ecosystem plugin: no dsh.bundle declaration
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
77c677github◼ 4 ecosystem app2026-09-11
https://github.com/hxwi1/dsh-desktop-window
◼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/hxwi1/dsh-desktop-window (version unstated)
ID: dsh-desktop-window-2@77c677@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
L1-L3 backfilled from dsh-desktop-window-2@dcf096…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-desktop-window-2@dcf096…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-desktop-window-2@dcf096…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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/hxwi1/dsh-desktop-window (version unstated)
ID: dsh-desktop-window-2@77c677@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
L1-L3 backfilled from dsh-desktop-window-2@dcf096…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-desktop-window-2@dcf096…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-desktop-window-2@dcf096…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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/hxwi1/dsh-desktop-window (version unstated)
ID: dsh-desktop-window-2@77c677@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
L1-L3 backfilled from dsh-desktop-window-2@dcf096…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-desktop-window-2@dcf096…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-desktop-window-2@dcf096…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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-alpha.12026-09-02Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.2-alpha.1
- • Plugin artifact: artifact unstated (historical)
ID: dsh-desktop-window-2@77c677@dsh0.1.2-alpha.1 · profile: l5-web-smoke
Issued: 2026-09-02 · expires: 2026-12-01
View checks & evidence
L1-L3 backfilled from dsh-desktop-window-2@dcf096…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-desktop-window-2@dcf096…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-desktop-window-2@dcf096…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
ecosystem plugin: no dsh.bundle declaration
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
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-window-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 medium (authoritative when present) → overall medium.
v0.1.00.1.0git2026-11-170.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningchildProcess · code-exec
plugin/index.js:23spawn('taskkill', ['/pid', String(child.pid), '/T', '/F'], { windowsHide: true }) - warningchildProcess · code-exec
plugin/index.js:39const child = spawn(electron, [appDir], { - warningchildProcess · code-exec
start.mjs:84const child = spawn(commandLine, { stdio: 'inherit', cwd, shell: isWin }) - warningshellExec · shell
stop.mjs:8const out = execFileSync('netstat', ['-ano', '-p', 'tcp'], { encoding: 'utf8' }) - warningshellExec · shell
stop.mjs:17const out = execFileSync('lsof', ['-ti', `tcp:${port}`], { encoding: 'utf8' }) - warningshellExec · shell
stop.mjs:34execFileSync('taskkill', ['/pid', String(pid), '/T', '/F'], { stdio: 'inherit' })
show 3 audit findings
- mediumUnescaped directory path interpolated into YAML patch enables plugin-entry injection
start.mjs:57pluginUrl comes from pathToFileURL(path.join(pluginDir,...)), and pathToFileURL does not percent-encode a single quote. If the install directory name contains a quote (e.g. a plugin unzipped into a crafted folder name), the single-quoted YAML scalar can be broken and extra 'insert' plugin entries with arbitrary 'name:' module specifiers injected; the resulting patch is passed to 'dsh web --patch', causing arbitrary module import/execution in the dsh process. Precondition: attacker-influenced folder name plus the user running start.mjs manually.
- lowstop.mjs terminates any process listening on port 3080 without ownership check
stop.mjs:31pidsOnPort collects every PID listening on TCP 3080 (lsof/netstat) and the loop force-kills each (SIGKILL via taskkill /F on Windows). If an unrelated service occupies 3080, running the helper destroys it. Impact is limited to explicit user action and a port collision, and no attacker input flows into the pids.
- lowWindows spawn of a joined command string with shell:true
start.mjs:85On Windows the joined command line runs through the shell. cmd/args are hardcoded and only the tmp patch path is interpolated, so exploitation requires tmpdir to contain shell metacharacters, but this pattern is fragile and turns any future dynamic value into command injection.
Runtime plugin only spawns a local Electron window, but start.mjs injects an unescaped path into a YAML patch and stop.mjs kills whatever listens on port 3080.
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-14 · activity: Inactive
• Repo created: 2026-08-14
• 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-window?
dsh-desktop-window 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-window?
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.
