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. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.Install verification details →
Data as of (UTC)
What it doesAI
Chromium browser extension to launch, stop, and restart local DeepSeek Harness from toolbar
- Start, stop, restart DeepSeek Harness from browser toolbar
- Auto-detects whether local page is reachable
- Requires Node.js; uses local assistant for process control
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:hahaha-taotao/dsh-browser-launcherInstall method: GitHub · runtime test inconclusive (L5 unknown) · verified on dsh 0.2.2-rc.3
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.
9 samples (roughly every 7 days), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-17 → 11-17 · 9 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-24 → 11-17 · 8 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
package manifest not collected — the declared range is unknown.
| plugin \ dsh | dsh 0.2.2-rc.3 | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| bc7491 | · | ○ | ○ | ○ | ○ |
| 22b622 | ○ | · | · | · | · |
bc7491github○ 18 ecosystem plugin2026-11-05
https://github.com/hahaha-taotao/dsh-browser-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/hahaha-taotao/dsh-browser-launcher (version unstated)
ID: dsh-browser-launcher@bc7491@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
View checks & evidence
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@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.2.1-rc.52026-10-31Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/hahaha-taotao/dsh-browser-launcher (version unstated)
ID: dsh-browser-launcher@bc7491@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@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.2.1-rc.32026-10-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/hahaha-taotao/dsh-browser-launcher (version unstated)
ID: dsh-browser-launcher@bc7491@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@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.2.1-rc.22026-10-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/hahaha-taotao/dsh-browser-launcher (version unstated)
ID: dsh-browser-launcher@bc7491@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@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.2.1-alpha.42026-10-18Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/hahaha-taotao/dsh-browser-launcher (version unstated)
ID: dsh-browser-launcher@bc7491@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@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.2.1-alpha.22026-10-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/hahaha-taotao/dsh-browser-launcher (version unstated)
ID: dsh-browser-launcher@bc7491@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@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.2.0-rc.22026-10-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/hahaha-taotao/dsh-browser-launcher (version unstated)
ID: dsh-browser-launcher@bc7491@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@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.7-rc.22026-09-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/hahaha-taotao/dsh-browser-launcher (version unstated)
ID: dsh-browser-launcher@bc7491@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@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.7-rc.12026-09-23Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/hahaha-taotao/dsh-browser-launcher (version unstated)
ID: dsh-browser-launcher@bc7491@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.7-alpha.22026-09-23Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/hahaha-taotao/dsh-browser-launcher (version unstated)
ID: dsh-browser-launcher@bc7491@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@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.6-alpha.22026-09-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/hahaha-taotao/dsh-browser-launcher (version unstated)
ID: dsh-browser-launcher@bc7491@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-19 · expires: 2026-09-26
View checks & evidence
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@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.6-alpha.12026-09-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/hahaha-taotao/dsh-browser-launcher (version unstated)
ID: dsh-browser-launcher@bc7491@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@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.5-rc.22026-09-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/hahaha-taotao/dsh-browser-launcher (version unstated)
ID: dsh-browser-launcher@bc7491@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@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 plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/hahaha-taotao/dsh-browser-launcher (version unstated)
ID: dsh-browser-launcher@bc7491@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@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 plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/hahaha-taotao/dsh-browser-launcher (version unstated)
ID: dsh-browser-launcher@bc7491@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@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-rc.12026-09-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: artifact unstated (historical)
ID: dsh-browser-launcher@bc7491@dsh0.1.2-rc.1 · profile: l4-sandbox
Issued: 2026-09-04 · expires: 2026-09-11
View checks & evidence
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
This level was not executed in this scan.
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 plugin
- • Node.js: v24.14.0
- • DSH: 0.1.2-alpha.1
- • Plugin artifact: artifact unstated (historical)
ID: dsh-browser-launcher@bc7491@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-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@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.
○prehistory2026-10-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/hahaha-taotao/dsh-browser-launcher (version unstated)
ID: dsh-browser-launcher@bc7491@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@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.
22b622github○ 1 ecosystem plugin2026-11-15
https://github.com/hahaha-taotao/dsh-browser-launcher
○dsh 0.2.2-rc.32026-11-15Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/hahaha-taotao/dsh-browser-launcher#22b6220217d04bfb61bb0a8cc56ac5e858c43feb
ID: dsh-browser-launcher@22b6220217d04bfb61bb0a8cc56ac5e858c43feb@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-15 · expires: 2026-11-22
View checks & evidence
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-browser-launcher@22b622…@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.
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-browser-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.
—22b6220217d0git2026-11-1922b6220217d0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (9)
- warningnetIp · network
extension/background.js:2const DEFAULT_URL = "http://127.0.0.1:3080/"; - warningnetIp · network
extension/popup.js:1const URL = "http://127.0.0.1:3080/"; - warningnetIp · network
extension/popup.js:79el.url.textContent = "http://127.0.0.1:3080"; - warningchildProcess · code-exec
host/native-host.js:121const result = spawnSync("netstat", ["-ano", "-p", "TCP"], { - warningchildProcess · code-exec
host/native-host.js:163const child = spawn("npx", ["--yes", "@deepseek-ai/dsh", "web"], { - warningchildProcess · code-exec
host/native-host.js:195const result = spawnSync("powershell.exe", ps, { - warningnetIp · network
host/native-host.js:11const URL = "http://127.0.0.1:3080"; - warningfsWrite · files
host/native-host.js:20fs.appendFileSync(LOG_PATH, `${new Date().toISOString()} ${line}\n`); - warningfsWrite · files
host/native-host.js:36fs.writeFileSync(STATE_PATH, JSON.stringify(state, null, 2));
show 3 audit findings
- mediumNative host executes unpinned package fetched from npm via 'npx --yes' on every start
host/native-host.js:163The 'start' action spawns 'npx --yes @deepseek-ai/dsh web' (Windows path builds the same command at line 187) with the user's full privileges and env. Neither a version nor an integrity hash is pinned, so whatever the npm registry serves for the package at click time is downloaded and executed; a hijacked/typo-squatted release or a malicious registry response becomes local code execution without further user interaction. npm_config_yes is also forced on, suppressing the usual confirmation prompt.
- lowbackground.js opens any URL supplied in a runtime message without validating sender
extension/background.js:23The service worker trusts message.url and does not inspect the _sender argument, so any extension context that can reach chrome.runtime.sendMessage (a future content script, an externally_connectable page, or a compromised extension page) could force the browser to open arbitrary URLs with no user gesture. In the harvested files no content script or externally_connectable declaration exists, so today only the plugin's own popup is a reachable sender and the impact is a hardening gap.
- lowStop path force-kills PIDs sourced from a user-writable state file
host/native-host.js:232killPid/collectStopPids act on PIDs read from ~/.dsh/launcher-state.json as well as the port-3080 listener, and use taskkill /T /F (or process.kill(-pid)) with no ownership check that the target is really the DSH process. An attacker able to tamper with that file could get an arbitrary same-user process tree force-killed; because the file is already writable by the same user, this grants no privilege escalation and is a robustness gap rather than an escalation path.
Local launcher plugin with no critical/high issue; the native host runs unpinned 'npx --yes @deepseek-ai/dsh web' fetched from the npm registry on every start, plus minor unvalidated-message gaps.
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-18 · activity: Inactive
• Repo created: 2026-08-18
• 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-browser-launcher?
dsh-browser-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. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.
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-browser-launcher?
Run dsh plugin --profile web add github:hahaha-taotao/dsh-browser-launcher 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. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.
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-19 (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.
