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
Background launcher for DeepSeek Harness with system tray support.
- System tray support for quick access
- Runs DeepSeek Harness in background
- CLI-based dsh plugin
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:wyf-777/deepseek-launcher#v1.2.1Install 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.
7 samples (roughly every 7 days), 2 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-08 · 7 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-01 → 11-08 · 6 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 |
|---|---|---|---|---|---|
| v1.2.1 | ○ | ○ | ○ | ○ | ○ |
v1.2.1github○ 16 ecosystem plugin2026-11-14
https://github.com/wyf-777/deepseek-launcher
○dsh 0.2.2-rc.12026-11-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/wyf-777/deepseek-launcher#v1.2.1
ID: deepseek-launcher@v1.2.1@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
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-31Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/wyf-777/deepseek-launcher#v1.2.1
ID: deepseek-launcher@v1.2.1@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
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-27Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/wyf-777/deepseek-launcher#v1.2.1
ID: deepseek-launcher@v1.2.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-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/wyf-777/deepseek-launcher#v1.2.1
ID: deepseek-launcher@v1.2.1@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-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.2.1-alpha.42026-10-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/wyf-777/deepseek-launcher#v1.2.1
ID: deepseek-launcher@v1.2.1@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
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-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/wyf-777/deepseek-launcher#v1.2.1
ID: deepseek-launcher@v1.2.1@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-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.2.0-rc.22026-10-08Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/wyf-777/deepseek-launcher#v1.2.1
ID: deepseek-launcher@v1.2.1@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.2.0-rc.12026-09-29Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/wyf-777/deepseek-launcher#v1.2.1
ID: deepseek-launcher@v1.2.1@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-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.1.7-rc.22026-09-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/wyf-777/deepseek-launcher#v1.2.1
ID: deepseek-launcher@v1.2.1@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-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.1.6-alpha.22026-09-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/wyf-777/deepseek-launcher#v1.2.1
ID: deepseek-launcher@v1.2.1@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/wyf-777/deepseek-launcher#v1.2.1
ID: deepseek-launcher@v1.2.1@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/wyf-777/deepseek-launcher#v1.2.1
ID: deepseek-launcher@v1.2.1@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/wyf-777/deepseek-launcher#v1.2.1
ID: deepseek-launcher@v1.2.1@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/wyf-777/deepseek-launcher#v1.2.1
ID: deepseek-launcher@v1.2.1@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/wyf-777/deepseek-launcher#v1.2.1
ID: deepseek-launcher@v1.2.1@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-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/wyf-777/deepseek-launcher#v1.2.1
ID: deepseek-launcher@v1.2.1@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-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.
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/deepseek-launcher/?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.1v1.2.1git2026-11-14v1.2.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (12)
- warningchildProcess · code-exec
deepseek.js:159spawn('cmd.exe', ['/c', 'start', '', url], { detached: true, stdio: 'ignore', windowsHide: true }).unref() - warningchildProcess · code-exec
deepseek.js:161spawn('open', [url], { detached: true, stdio: 'ignore' }).unref() - warningchildProcess · code-exec
deepseek.js:163spawn('xdg-open', [url], { detached: true, stdio: 'ignore' }).unref() - warningshellExec · shell
deepseek.js:71execFileSync(wscript, [launchScript], { - warningshellExec · shell
deepseek.js:110return execFileSync('powershell.exe', ['-NoProfile', '-Command', script], { - warningshellExec · shell
deepseek.js:114return execFileSync('ps', ['-p', String(pid), '-o', 'args='], { - warningfsWrite · files
deepseek.js:92fs.writeFileSync(file, String(pid) + '\n') - warningfsWrite · files
deepseek.js:171fs.appendFileSync(LOG_FILE, `\n[launcher ${new Date().toISOString()}] starting ${spec} web\n`) - warningfsWrite · files
deepseek.js:208const logStream = fs.createWriteStream(LOG_FILE, { flags: 'a' }) - warningchildProcessImport · code-exec
launcher-updater.js:9const { spawn, spawnSync } = require('node:child_process') - warningfsWrite · files
launcher-updater.js:136fs.writeFileSync(temporary, `${JSON.stringify(state, null, 2)}\n`, { encoding: 'utf8', mode: 0o600 }) - warningfsWrite · files
launcher-updater.js:526fs.writeFileSync(temporary, buffer)
show 4 audit findings
- mediumDSH_PACKAGE env var is used verbatim as an executable npm package spec (no validation)
deepseek.js:451resolveHarnessSpec feeds this value into `spawn('npx', ['--yes', 'pnpm@10.34.5', 'dlx', spec, 'web', ...])` (deepseek.js:207) and into `'-Spec', spec` for start-server.ps1 (deepseek.js:182). Whoever can set an environment variable for the user's session (shell profile, CI, parent process, wrapper scripts) gets arbitrary npm package code executed with the user's privileges and no confirmation prompt, simply because the user runs `deepseek start`. DSH_PORT is range-checked but DSH_PACKAGE is not checked at all.
- lowHarness is fetched and executed unpinned (default @deepseek-ai/dsh@latest) on every start
deepseek.js:207When no cached harness version is found, resolveHarnessSpec returns `@deepseek-ai/dsh@latest` (deepseek.js:453) and the launcher auto-confirms with `--yes`, so whatever the npm registry currently serves under that name is downloaded and executed without user review or integrity check (no hash/signature, unlike the launcher installer path). A hijacked or maliciously published package would run with the user's privileges.
- lowSelf-update downloads and executes a Windows installer whose only integrity anchor is a checksum from the same release
launcher-updater.js:603performUpdate/performRollback fetch `deepseek-launcher-windows-setup.exe` plus its `.sha256` from the same GitHub release (launcher-updater.js:586-588) and then execute the exe. This is the tool's own update channel, so a compromise of the wyf-777 GitHub account/repository (or of GitHub release assets) yields arbitrary code execution on every user machine, and the checksum provides no protection because it is served by the same compromised source. Mitigations present: URL pinning to github.com/wyf-777/deepseek-launcher/releases/download/<tag>/<asset>, SHA-256 verification, Windows-only, and a
- lowExecutionPolicy Bypass runs unharvested PowerShell helpers with start-server/tray arguments
deepseek.js:181start-server.ps1, start-tray.ps1, autostart.ps1 and launch.vbs are listed in package.json 'files' and are executed on every start/autostart with the user's privileges, but they were not part of the audited source (HARVESTED contains only 4 JS/JSON files). The `-Spec` value can also be attacker-influenced via DSH_PACKAGE, so any argument handling flaw inside the PS1 would be a real code-execution path; that risk cannot currently be excluded.
Legit DSH background launcher/tray; main risks are the unvalidated DSH_PACKAGE spec executed as an npm package and self-update running a downloaded Windows installer.
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-06 · activity: Stable
• Repo created: 2026-08-14
• Stars: ★ 5 · Forks: 0
• Health: Stable — committed within 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 deepseek-launcher?
deepseek-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 deepseek-launcher?
Run dsh plugin --profile web add github:wyf-777/deepseek-launcher#v1.2.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-11-14 (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.