Install verification: sandbox install failed (L4) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Lets a DSH agent drive a real local Chrome browser through the browser-use Browser Harness, with no API key required.
- Drives a real local Chrome browser from a DSH agent
- Built on the browser-use Browser Harness (CDP-based)
- No API key or cloud service needed
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.
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); the npm pair from every snapshot.
6 samples (roughly every 7 days), 3 of them reconstructed (hollow dots); sampled points, not a daily series
09-22 → 10-26 · 6 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-06 → 10-26 · 4 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-21 → 10-30 · 38 points
The snapshot’s last-week rolling window (official npm + npmmirror combined)
09-21 → 10-30 · 38 points
Installation
dsh plugin --profile web add dsh-browser-harnessInstall method: npm · sandbox install failed (L4)
Verification & Compatibility
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
Based on a single engines.dsh range (decides alone; peerDependencies is not consulted). raw ranges
>=0.1.0-rc.6 <0.2.0
✗ Running dsh 0.2.1-rc.5 is outside the declared range — the official install gate rejects it (incompatible-version).
To force-install, grant an exact-version exemption: dsh plugin allow-version dsh-browser-harness@0.4.4 0.2.1-rc.5 (the exemption lives in the local profile; this site does not assume one)
Deciding channel: since 0.2.1-alpha.4 DSH judges by engines.dsh when declared — peerDependencies is then not consulted.
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| plugin ＼ dsh | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| 0.4.4 | · | · | ✓ | ✓ | ✓ |
| 0.4.1 | · | · | · | · | · |
| 0.4.0 | · | · | · | · | · |
| 0.2.0 | · | · | · | · | · |
| 0.1.0 | · | · | · | · | · |
0.4.4npm✓ 6 runtime-verified2026-10-30
dsh-browser-harness
✓dsh 0.2.1-rc.22026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-browser-harness@0.4.4
ID: dsh-browser-harness@0.4.4@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
active in loader tree (150 entries)
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-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-browser-harness@0.4.4
ID: dsh-browser-harness@0.4.4@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
View checks & evidence
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
active in loader tree (150 entries)
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-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-browser-harness@0.4.4
ID: dsh-browser-harness@0.4.4@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
active in loader tree (150 entries)
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-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-browser-harness@0.4.4
ID: dsh-browser-harness@0.4.4@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
active in loader tree (150 entries)
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-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-browser-harness@0.4.4
ID: dsh-browser-harness@0.4.4@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓prehistory2026-10-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-browser-harness@0.4.4
ID: dsh-browser-harness@0.4.4@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.4.1npm✓ 2 runtime-verified2026-09-26
dsh-browser-harness
✓dsh 0.1.7-rc.22026-09-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-browser-harness@0.4.1
ID: dsh-browser-harness@0.4.1@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
active in loader tree (150 entries)
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-24L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · dsh-browser-harness@0.4.1
ID: dsh-browser-harness@0.4.1@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
View checks & evidence
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.4.0npm2026-09-21
dsh-browser-harness
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.2.0npm2026-09-20
dsh-browser-harness
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.1.0npm✓ 1 runtime-verified2026-09-20
dsh-browser-harness
✓dsh 0.1.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · dsh-browser-harness@0.1.0
ID: dsh-browser-harness@0.1.0@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-browser-harness@0.4.4@dsh0.2.1-rc.5 (l3-fullscan)
active in loader tree (150 entries)
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-browser-harness/?ref=badge)``[](https://www.dsh.so/artifact/dsh-browser-harness/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-browser-harness/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-browser-harness/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-browser-harness/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-browser-harness/?ref=badge-install)`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.4.4dsh manifest0.4.4npm2026-11-020.4.4same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningchildProcess · code-exec
lib/index.js:128const probe = spawnSync('netstat', ['-ano'], { encoding: 'utf8', windowsHide: true, timeout: 15_000 }) - warningchildProcess · code-exec
lib/index.js:149const child = spawn(chrome, args, { detached: true, stdio: 'ignore', windowsHide: false }) - warningchildProcess · code-exec
lib/index.js:180child = spawn(cmd, [], { env, windowsHide: true, stdio: ['pipe', 'pipe', 'pipe'] }) - warningnetIp · network
lib/index.js:130if (listening) return { ok: true, cdpUrl: `http://127.0.0.1:${cfg.cdpPort}` } - warningnetIp · network
lib/index.js:151return { ok: true, cdpUrl: `http://127.0.0.1:${cfg.cdpPort}`, launched: true } - warningnetIp · network
lib/index.js:345return `http://127.0.0.1:${cfg.cdpPort}`
show 2 audit findings
- mediumbrowser_run executes arbitrary agent-supplied Python on the host, reachable via indirect prompt injection
lib/index.js:224The browser_run tool feeds model-authored Python into the browser-use/browser-harness CLI, which runs with the DSH host user's privileges. The same agent browses untrusted web pages, so a malicious page can prompt-inject the model into calling browser_run to read/exfiltrate local files or credentials, or launch host processes (host-level RCE).
- lowAPI keys are passed via env to a config-defined autopilot command that may be fetched at runtime
lib/index.js:277TypeSafe/TextModel keys are placed in the environment of a config-defined autopilot command. If that command is a runtime fetcher such as `uvx jev-ultrafast`, the fetched package can read and exfiltrate the keys; the runner's supply chain can also compromise them. Not enabled by default (command empty).
Agent-supplied Python is piped to the browser-use CLI and executed host-side; browsing untrusted pages can escalate via indirect prompt injection. No other high-risk constructs found.
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-25 · activity: Stable
• Repo created: 2026-09-18
• Stars: ★ 0 · 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 @chaserchan/dsh-browser-harness?
@chaserchan/dsh-browser-harness is a DeepSeek Harness (dsh) plugin listed on dsh.so — an independent community registry that indexes public source repositories and publishes automated security-scan and install-verification results for each entry.
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 @chaserchan/dsh-browser-harness?
Run dsh plugin --profile web add dsh-browser-harness in a DeepSeek Harness (dsh) environment. The command is parsed from the plugin manifest and its install spec is verified (L3); runtime sandbox install testing may not have run yet.
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-02 (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.