DSH Launch Console是Deepseek Harness的极轻量化启动器，无需终端命令即可启动 DSH，可管理DSH版本和插件。DSH Launch Console is an ultra-lightweight launcher for DeepSeek Harness. It lets you start DSH without any terminal commands, and manage DSH versions and plugins.
Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
Data as of (UTC)
What it doesAI
Rust desktop launcher that silently starts the DSH service and hosts its Web UI in a locked, hardcoded-address window as one executable.
- Silently starts DSH; falls back to npx @deepseek ai/dsh web if not installed
- Locked micro-browser window that only visits the hardcoded DSH address
- Builds to a single executable with no terminal window; Windows and Linux/macOS variants
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 github:CosmoSail/DSH_Launch_Console#v0.3.1Install method: GitHub · runtime test inconclusive (L5 unknown)
Verification & Compatibility○ Ecosystem plugin
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
package manifest not collected — the declared range is unknown.
| plugin ＼ dsh | dsh 0.2.1-rc.3 current | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 |
|---|---|---|---|---|---|
| v0.3.1 | ○ | ○ | ○ | ○ | ○ |
| v0.1.0 | · | · | · | · | · |
v0.3.1github○ 5 ecosystem plugin2026-10-27
https://github.com/CosmoSail/DSH_Launch_Console
○dsh 0.2.1-rc.3current2026-10-27Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/CosmoSail/DSH_Launch_Console#v0.3.1
ID: dsh-launch-console@v0.3.1@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
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.2.1-rc.22026-10-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/CosmoSail/DSH_Launch_Console#v0.3.1
ID: dsh-launch-console@v0.3.1@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
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.2.1-alpha.42026-10-18Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/CosmoSail/DSH_Launch_Console#v0.3.1
ID: dsh-launch-console@v0.3.1@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
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.2.1-alpha.22026-10-12Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/CosmoSail/DSH_Launch_Console#v0.3.1
ID: dsh-launch-console@v0.3.1@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-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.2.0-rc.22026-10-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/CosmoSail/DSH_Launch_Console#v0.3.1
ID: dsh-launch-console@v0.3.1@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-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.
v0.1.0github○ 6 ecosystem plugin2026-10-01
github:CosmoSail/DSH_Launch_Console#v0.1.0
○dsh 0.2.0-rc.12026-09-30Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · github:CosmoSail/DSH_Launch_Console#v0.1.0#v0.1.0
ID: dsh-launch-console@v0.1.0@dsh0.2.0-rc.1 · profile: l5-web-smoke
Issued: 2026-09-30 · expires: 2026-12-29
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.7-rc.22026-09-27Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · github:CosmoSail/DSH_Launch_Console#v0.1.0#v0.1.0
ID: dsh-launch-console@v0.1.0@dsh0.1.7-rc.2 · profile: l5-web-smoke
Issued: 2026-09-27 · expires: 2026-12-26
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.6-alpha.22026-09-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/CosmoSail/DSH_Launch_Console#v0.1.0
ID: dsh-launch-console@v0.1.0@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
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.6-alpha.12026-09-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/CosmoSail/DSH_Launch_Console#v0.1.0
ID: dsh-launch-console@v0.1.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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.5-rc.22026-09-15Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/CosmoSail/DSH_Launch_Console#v0.1.0
ID: dsh-launch-console@v0.1.0@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-15 · expires: 2026-09-22
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.
○prehistory2026-10-01Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · github:CosmoSail/DSH_Launch_Console#v0.1.0#v0.1.0
ID: dsh-launch-console@v0.1.0@dshunknown · profile: l5-web-smoke
Issued: 2026-10-01 · expires: 2026-12-30
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-launch-console/?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.3.1git2026-10-29v0.3.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (9)
- warningnetIp · network
src/config.rs:219pub const DEFAULT_URL: &str = "http://127.0.0.1:3080"; - warningnetIp · network
src/dsh.rs:695let stale = b"dsh web: http://127.0.0.1:3080/?token=OLD\n"; - warningnetIp · network
src/dsh.rs:696let fresh = b"dsh web: http://127.0.0.1:3080/?token=NEW&x=1\n"; - warningnetIp · network
src/settings.rs:474"url": "http://127.0.0.1:3199", - warningnetIp · network
src/settings.rs:602s.url = "http://127.0.0.1:3080".into(); - warningnetIp · network
src/settings.rs:631s.url = "http://127.0.0.1:3080".into(); - warningnetIp · network
src/webui.rs:74let base = "http://127.0.0.1:3080"; - warningnetIp · network
src/webui.rs:75assert_eq!(build_url(base, Some("tok")), "http://127.0.0.1:3080/?token=tok"); - warningnetIp · network
src/webui.rs:76assert_eq!(build_url(base, None), "http://127.0.0.1:3080/");
show 3 audit findings
- mediumDSH web auth token is written into a predictable world-readable temp log
src/webui.rs:16open_web_ui calls build_url(base, token) which appends '?token=...', and open_url logs that full URL before launching the browser. config::log writes to std::env::temp_dir()/DSH-Launch-Console.log, created with default permissions and a fixed name, so any other local user (or anything that can read /tmp) can read the DSH web session token. The same token is also present in the child's stdout, which is redirected to another fixed temp file (config::instance_server_log), so the secret is exposed twice. A stolen token grants control of the running DSH agent on 127.0.0.1.
- lowSettings and logs live in the shared temp dir under fixed names, enabling local pre-creation/symlink tampering
src/config.rs:190data_dir() returns std::env::temp_dir() (src/config.rs:14) and the launcher reads/writes DSH-Launch-Console-settings.json, DSH-Launch-Console.log and DSH-Launch-Console-server-<id>.log there without any ownership, permission or symlink check. On a multi-user machine another local user can pre-create or symlink these predictable paths, feeding the launcher attacker-chosen settings (instance home/profile/port) or redirecting append-style log writes onto a file the victim can write. Impact is bounded to same-user file overwrite and configuration tampering.
- lowNetwork-derived URLs are handed to the OS protocol handler without scheme restrictions
src/webui.rs:22The URL is passed as an argv element (no shell injection), but on Windows rundll32 url.dll,FileProtocolHandler dispatches any registered protocol, and on Unix open::that() delegates to xdg-open. The URL values come from remote data: plugin market entries and GitHub search results (RowAction::OpenRepo(p.url.clone()) in src/app.rs) and plugin package.json repository fields, and are only opened after the user clicks a button. A crafted entry could therefore hand a non-http(s) scheme (e.g. file:, smb:, or another registered handler) to the OS handler.
No command injection: processes are spawned with argv arrays and version/slug inputs are sanitized; residual risk is the DSH web token written into a predictable shared temp log.
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-10-15 · activity: Active
• Repo created: 2026-09-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_Launch_Console?
DSH_Launch_Console is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
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_Launch_Console?
Run dsh plugin --profile web add github:CosmoSail/DSH_Launch_Console#v0.3.1 in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs.
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-10-29 (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.