Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.3 · last checked Install verification details →
Showing badges for the 5 most recent dsh versions; older ones are hidden.
Data as of (UTC)
What it doesAI
Chrome side panel embedding dsh web UI with host plugins for page reading, HTTP capture, and browser control.
- Embeds full dsh web UI in Chrome side panel
- Page reading plugin for capturing web content
- HTTP capture and browser control via host plugins
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-chromeInstall method: npm · runtime verified (L5)
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.
current (registry 2026-11-16) · 9 samples (roughly every 7 days), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-13 · 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
10-02 → 11-13 · 8 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-17 → 11-15 · 54 points
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
09-17 → 11-16 · 55 points
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 1 requirement(s) across 2 @deepseek-ai/dsh-* packages. raw ranges
* ×2
✓ Running dsh 0.2.2-rc.3 is within the declared range — install is not blocked by version.
Deciding channel: no engines.dsh declared, so every dsh* peer is checked (workspace:^ | ~ | * counts as the running version).
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| plugin \ dsh | dsh 0.2.2-rc.3 current | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| 0.1.3 | ✓ | ✓ | ✓ | ✓ | ✓ |
| v0.1.3 | · | · | · | · | · |
0.1.3npm✓ 14 runtime-verified◐ 1 testing2026-11-16
dsh-chrome
✓dsh 0.2.2-rc.3current2026-11-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: npm · dsh-chrome@0.1.3
ID: dsh-chrome-2@0.1.3@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-16 · expires: 2026-11-23
View checks & evidence
active in loader tree (208 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.2-rc.12026-11-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · dsh-chrome@0.1.3
ID: dsh-chrome-2@0.1.3@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-04 · expires: 2026-11-11
View checks & evidence
active in loader tree (152 entries)
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-31L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · dsh-chrome@0.1.3
ID: dsh-chrome-2@0.1.3@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
active in loader tree (152 entries)
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-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-chrome@0.1.3
ID: dsh-chrome-2@0.1.3@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
active in loader tree (152 entries)
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-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-chrome@0.1.3
ID: dsh-chrome-2@0.1.3@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
active in loader tree (152 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-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-chrome@0.1.3
ID: dsh-chrome-2@0.1.3@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
active in loader tree (152 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-10L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-chrome@0.1.3
ID: dsh-chrome-2@0.1.3@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
View checks & evidence
active in loader tree (152 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-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-chrome@0.1.3
ID: dsh-chrome-2@0.1.3@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
active in loader tree (152 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-29L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-chrome@0.1.3
ID: dsh-chrome-2@0.1.3@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
active in loader tree (152 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-25L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-chrome@0.1.3
ID: dsh-chrome-2@0.1.3@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
active in loader tree (152 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-chrome@0.1.3
ID: dsh-chrome-2@0.1.3@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
active in loader tree (152 entries)
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-23L4 · testing (install passed, runtime untested)
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: npm · dsh-chrome@0.1.3
ID: dsh-chrome-2@0.1.3@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
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.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · dsh-chrome@0.1.3
ID: dsh-chrome-2@0.1.3@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
active in loader tree (152 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-chrome@0.1.3
ID: dsh-chrome-2@0.1.3@dsh0.1.6-alpha.1 · profile: l3-fullscan
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
active in loader tree (152 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-chrome@0.1.3
ID: dsh-chrome-2@0.1.3@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
active in loader tree (152 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.1.3github✓ 3 runtime-verified2026-09-16
https://github.com/stuarthu/dsh-chrome
✓dsh 0.1.5-rc.22026-09-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/stuarthu/dsh-chrome#v0.1.3
ID: dsh-chrome-2@v0.1.3@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
active in loader tree (152 entries)
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-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/stuarthu/dsh-chrome#v0.1.3
ID: dsh-chrome-2@v0.1.3@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-16
View checks & evidence
active in loader tree (152 entries)
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-07L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/stuarthu/dsh-chrome#v0.1.3
ID: dsh-chrome-2@v0.1.3@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
active in loader tree (153 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-chrome-2/?ref=badge)``[](https://www.dsh.so/artifact/dsh-chrome-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-chrome-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-chrome-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-chrome-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-chrome-2/?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.1.3dsh manifest0.1.3npm2026-11-170.1.3same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningnetIp · network
bin/cli.js:67console.log(" 1. Make sure `dsh web` is running (default http://127.0.0.1:3080)."); - warningnetIp · network
extension/src/background.js:25const DEFAULT_DSH_URL = "http://127.0.0.1:3080"; - warningnetIp · network
extension/src/background.js:271res = await fetch(`http://127.0.0.1:${CDP_PORT}/json/list`, { signal }); - warningnetIp · network
extension/src/options.js:5$("dshUrl").value = stored.dsh_url || "http://127.0.0.1:3080"; - warningnetIp · network
extension/src/options.js:9const url = $("dshUrl").value.trim().replace(/\/+$/, "") || "http://127.0.0.1:3080"; - warningnetIp · network
extension/src/sidepanel.js:44const url = stored.dsh_url || "http://127.0.0.1:3080";
show 4 audit findings
- mediumUnauthenticated loopback bridge: any client can push page frames and receive browser tool actions
host/bridge.js:106The /dsh-agent/bridge upgrade handler performs no token, Origin or peer check, and call() addresses the most recently connected socket (`const ws = [...sockets].at(-1)`, line 159). Any local process — and any web page that can open a WebSocket to 127.0.0.1:3080, since WebSockets are not stopped by the same-origin policy and only a server-side Origin check would block them, which is absent here — can (a) send {type:"page"} frames that are injected verbatim into the user's most recently active agent session as 'current page' content (prompt-injection channel), and (b) become the socket that brow
- lowRemote-CDP fallback trusts webSocketDebuggerUrl from 127.0.0.1:9222 without validating host or scheme
extension/src/background.js:271The debugger URLs returned by /json/list are opened directly (`ws = new WebSocket(wsUrl)`, around line 307) with no check that they are ws:// on loopback and on CDP_PORT. A local process squatting on port 9222 (Chrome not running yet, or a non-Chrome service) can return a fake target list whose webSocketDebuggerUrl points at an arbitrary host; the extension then sends Runtime.evaluate frames there and accepts the arbitrary reply as page text or as a successful click. Only reachable when the user follows the documented --remote-debugging-port=9222 setup.
- lowUser-configurable dsh_url lets the extension stream active-tab text to any host
extension/src/options.js:9Whatever absolute URL is stored is used as the bridge target (`sock = new WebSocket(`${dshUrl.replace(/^http/, "ws")}/dsh-agent/bridge`)`, extension/src/background.js:106) and receives every auto-pushed page (URL, title, up to 1MB of body text) and drives the browser actions. Only this extension's options page writes the value, so the risk is misconfiguration or a mis-set profile, but there is no scheme/host restriction and no warning that a non-loopback destination exports page contents off the machine.
- lowOne broad keyword in a user message unlocks navigate/click/open_tab for the whole turn
host/intent-gate.js:30Any occurrence of e.g. 'tab', 'open', 'visit' or '点击' in any real user message of the current turn unlocks navigation, clicking and tab creation (host/browser-tools.js isUnlocked path; the plugin itself calls this best-effort). Page content injected as source.kind="plugin" during such a turn is attacker-controlled, so a benign incidental word plus model gullibility is enough for a page-driven gated action; no per-action confirmation exists.
Careful browser-automation plugin; real residual risk is an unauthenticated loopback WebSocket bridge (page-frame injection / action hijack) plus an unvalidated remote-CDP endpoint.
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-22 · activity: Stable
• Repo created: 2026-08-15
• Stars: ★ 12 · Forks: 7
• Health: Stable — committed within 90 days
Source
GitHub: github.com/stuarthu/dsh-chrome
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-chrome?
dsh-chrome 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-chrome?
Run dsh plugin --profile web add dsh-chrome 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-11-17 (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.
