⚠️ This repository has been renamed: imroc/dsh-embedded-browser — click to visit the new location. Everything below is preserved as originally indexed.
Install verification: runtime verified (L5) · tested on dsh 0.2.0-rc.2 · last checked Install verification details →
Data as of (UTC)
What it doesAI
A shared browser tab in DeepSeek Harness that the AI drives via browser_panel_* tools while users watch or take over for logins, 2FA and QR codes.
- AI drives a browser via browser_panel_* tools
- Users watch or take over the same tab live in DSH Web UI
- Handles logins, 2FA and QR code steps
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 dsh-browser-panelInstall method: GitHub · runtime verified (L5) · verified on dsh 0.2.0-rc.2
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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin ＼ dsh | dsh 0.2.0-rc.2 | dsh 0.2.0-rc.1 | dsh 0.1.7-rc.2 | dsh 0.1.7-rc.1 | dsh 0.1.6-alpha.2 |
|---|---|---|---|---|---|
| v0.3.0 | ◐ | · | · | · | · |
| 0.2.0 | ✓ | ✓ | ✓ | ✓ | ✓ |
v0.3.0github◐ 1 testing2026-10-09
https://github.com/imroc/dsh-browser-panel
◐dsh 0.2.0-rc.22026-10-09L4 · testing (install passed, runtime untested)
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/imroc/dsh-browser-panel#v0.3.0
ID: dsh-browser-panel@v0.3.0@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-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
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.
0.2.0npm✓ 8 runtime-verified2026-10-09
dsh-browser-panel
✓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-panel@0.2.0
ID: dsh-browser-panel@0.2.0@dsh0.2.0-rc.2 · profile: l5-web-smoke
Issued: 2026-10-09 · expires: 2027-01-07
View checks & evidence
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
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-panel@0.2.0
ID: dsh-browser-panel@0.2.0@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-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
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.22026-09-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-browser-panel@0.2.0
ID: dsh-browser-panel@0.2.0@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-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
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-23L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · dsh-browser-panel@0.2.0
ID: dsh-browser-panel@0.2.0@dsh0.1.7-rc.1 · profile: l3-fullscan
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
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.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · dsh-browser-panel@0.2.0
ID: dsh-browser-panel@0.2.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-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
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.6-alpha.12026-09-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · dsh-browser-panel@0.2.0
ID: dsh-browser-panel@0.2.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
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.5-rc.22026-09-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: npm · dsh-browser-panel@0.2.0
ID: dsh-browser-panel@0.2.0@dsh0.1.5-rc.2 · profile: l3-fullscan
Issued: 2026-09-15 · expires: 2026-09-22
View checks & evidence
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
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-panel@0.2.0
ID: dsh-browser-panel@0.2.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
↳ carried from earlier record dsh-browser-panel@v0.3.0@dsh0.2.0-rc.2 (l4-sandbox)
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-panel/?ref=badge)``[](https://www.dsh.so/artifact/dsh-browser-panel/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-browser-panel/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-browser-panel/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-browser-panel/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-browser-panel/?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.3.0dsh manifestv0.3.0git2026-10-08v0.3.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (4)
- warningchildProcess · code-exec
lib/browser.js:413this.chrome = spawn(this.executable, args, { env, stdio: ['ignore', 'pipe', 'pipe'] }) - warningchildProcess · code-exec
lib/browser.js:446this.xvfb = spawn(xvfb, [display, '-screen', '0', screen, '-nolisten', 'tcp', '-noreset'], { - warningnetIp · network
lib/cdp.js:171const response = await fetch(`http://127.0.0.1:${this.port}/json/list`) - warningnetIp · network
lib/cdp.js:293const response = await fetch(`http://127.0.0.1:${port}/json/version`)
show 4 audit findings
- mediumChrome runs with --no-sandbox when the DSH host runs as root, rendering untrusted web pages unsandboxed
lib/browser.js:406The plugin's whole purpose is to navigate the AI to arbitrary, potentially hostile web pages. In a root container/host (a very common DSH deployment) the renderer sandbox is disabled, so any Chrome renderer/GPU compromise from page content yields code execution as uid 0 inside the host or container, with access to the persistent login profile.
- lowDevTools endpoint started with --remote-allow-origins=* on the port that drives the shared logged-in profile
lib/browser.js:394This disables Chrome's WebSocket Origin check on the loopback DevTools port. Anyone who can reach ws://127.0.0.1:<port> (a local process, a sidecar container sharing the netns, or a malicious page that manages to learn the port and browser UUID) can attach and fully drive the browser that holds every site login, bypassing the intended restriction. Practical exploitation is limited by Chrome's loopback Host-header check and SOP on /json/version, hence low.
- lowPersistent login profile created with default permissions and a basic password store
lib/browser.js:365The Chrome user-data-dir that keeps cookies and saved logins for every site is created with the process umask (typically 0755), and --password-store=basic encrypts the cookie DB with a hardcoded key. On a host with other local accounts, those accounts can read and decrypt the human's authenticated sessions.
- lowControl routes trust a client-supplied sessionId with no ownership check
lib/routes.js:134Every route is authenticated by the GUI's own guard, but /open, /close, /human-done, /state and the /stream upgrade accept any sessionId the caller names. A caller holding the GUI cookie but acting for session A can open, screenshot-stream (via the socket), or close session B's tab, or settle session B's pending human hand-over. On a single-operator host this is only a robustness gap; it becomes cross-session data exposure if one DSH web origin ever serves more than one user or untrusted automation.
No critical issues: routes are auth-guarded and shell-free; risk sits in Chrome launch flags (--no-sandbox as root, --remote-allow-origins=*) plus unharvested ws/tools/screencast modules.
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-23 · activity: Stable
• Repo created: 2026-09-14
• Stars: ★ 0 · Forks: 2
• 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 dsh-browser-panel?
dsh-browser-panel 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 dsh-browser-panel?
Run dsh plugin --profile web add github:imroc/dsh-browser-panel#v0.3.0 in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4) plus web smoke testing (L5).
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-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.