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
Launcher for DeepSeek Harness: auto-finds packages, starts WebUI in embedded windows, and manages packages/configs/plugins/multi-window.
- Auto-finds user packages and launches WebUI in embedded windows
- Provides package, config, and plugin management tools
- Supports multi-window operation for concurrent sessions
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:WEP-56/DSH-Launcher#v0.7.2Install method: GitHub · runtime test inconclusive (L5 unknown) · 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.
10 samples (roughly every 7 days), 5 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-08 · 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
09-28 → 11-08 · 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 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
○ 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.4 |
|---|---|---|---|---|---|
| v0.7.2 | ○ | ○ | ○ | ○ | ○ |
v0.7.2github○ 15 ecosystem plugin2026-11-13
https://github.com/WEP-56/DSH-Launcher
○dsh 0.2.2-rc.12026-11-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/WEP-56/DSH-Launcher#v0.7.2
ID: dsh-launcher-6@v0.7.2@dsh0.2.2-rc.1 · profile: l3-fullscan
Issued: 2026-11-04 · expires: 2026-11-11
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.52026-10-30Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/WEP-56/DSH-Launcher#v0.7.2
ID: dsh-launcher-6@v0.7.2@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-30 · expires: 2026-11-06
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.32026-10-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/WEP-56/DSH-Launcher#v0.7.2
ID: dsh-launcher-6@v0.7.2@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
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-18Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/WEP-56/DSH-Launcher#v0.7.2
ID: dsh-launcher-6@v0.7.2@dsh0.2.1-rc.2 · 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.42026-10-15Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/WEP-56/DSH-Launcher#v0.7.2
ID: dsh-launcher-6@v0.7.2@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-15 · expires: 2026-10-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.
○dsh 0.2.1-alpha.22026-10-10Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/WEP-56/DSH-Launcher#v0.7.2
ID: dsh-launcher-6@v0.7.2@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
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-08Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/WEP-56/DSH-Launcher#v0.7.2
ID: dsh-launcher-6@v0.7.2@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-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.7-rc.22026-09-25Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/WEP-56/DSH-Launcher#v0.7.2
ID: dsh-launcher-6@v0.7.2@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
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/WEP-56/DSH-Launcher#v0.7.2
ID: dsh-launcher-6@v0.7.2@dsh0.1.6-alpha.2 · profile: l3-fullscan
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/WEP-56/DSH-Launcher#v0.7.2
ID: dsh-launcher-6@v0.7.2@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-13Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/WEP-56/DSH-Launcher#v0.7.2
ID: dsh-launcher-6@v0.7.2@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-13 · expires: 2026-09-20
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 plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/WEP-56/DSH-Launcher#v0.7.2
ID: dsh-launcher-6@v0.7.2@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 plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/WEP-56/DSH-Launcher#v0.7.2
ID: dsh-launcher-6@v0.7.2@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 plugin
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/WEP-56/DSH-Launcher#v0.7.2
ID: dsh-launcher-6@v0.7.2@dsh0.1.2-rc.1 · profile: l3-fullscan
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.
○prehistory2026-10-02Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · github:WEP-56/DSH-Launcher#v0.7.2#v0.7.2
ID: dsh-launcher-6@v0.7.2@dshunknown · profile: l5-web-smoke
Issued: 2026-10-02 · expires: 2026-12-31
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-launcher-6/?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.7.2v0.7.2git2026-11-13v0.7.2same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (2)
- criticaldestructiveRm · destructive
src-tauri/src/plugins.rs:507assert!(!is_safe_plugin_spec("pkg; rm -rf /")); - warningnetIp · network
src-tauri/src/state.rs:61url: "http://127.0.0.1:3080".into(),
show 3 audit findings
- mediumlist_config_files returns the raw .credentials.yaml content to any launcher webview over IPC
src-tauri/src/dsh_files.rs:64The `list_config_files` command (registered in lib.rs) reads the user's DSH credentials file and returns its full text in the ConfigFileInfo.content field with no per-window restriction and no user confirmation at call time. Any script that executes in a launcher webview — e.g. the UI renders remote-derived strings from the third-party market catalog (market.rs builds MarketPlugin fields such as description/homepage directly from dsh.aitreez.com) — can call this command and siphon long-lived API keys, and the same IPC surface also exposes install/update commands (code execution via npm/dsh).
- loweval() of an interpolated tab title in the drag-preview webview (mitigated by JSON string escaping)
src-tauri/src/windows_ui.rs:184The title argument is placed into JavaScript source and executed via eval inside a webview. serde_json::to_string escapes quotes, backslashes and control characters, so a breakout is not currently possible on modern WebView2/WebKit (U+2028/U+2029 are legal inside ES2019+ string literals); the residual risk is a fragile sink that would become script injection in the same webview if the escaping or engine assumptions change.
- lowProcess-launch layer exec.rs/service.rs is referenced but absent from the harvest, so shell-vs-argv semantics are unverified
src-tauri/src/lib.rs:17All dangerous operations (dsh/npm invocation, plugin install, dsh update) funnel through exec.rs/service.rs, which were not provided even though the manifest reports no unharvested files. Inputs crossing that boundary include the raw search query (`format!("{} dsh-plugin", query.trim())` in plugins.rs search_plugins) and plugin specs whose allowlist still permits spaces (`"@/._-:# +~=".contains(ch)`), so if that layer ever joins arguments through cmd.exe/sh, argument injection would be possible — this cannot be confirmed or ruled out from the reviewed source.
The scan's critical is not reproducible in the visible surface (eval is JSON-escaped, specs allowlisted), but the DSH credentials file is returned to the webview over IPC.
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-09-29 · activity: Stable
• Repo created: 2026-08-14
• Stars: ★ 32 · Forks: 2
• Health: Stable — committed within 90 days
Source
GitHub: github.com/WEP-56/DSH-Launcher
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-Launcher?
DSH-Launcher 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-Launcher?
Run dsh plugin --profile web add github:WEP-56/DSH-Launcher#v0.7.2 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-11-13 (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.