Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.1 · 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
自建 DSH 浏览器服务：单例 CDP 守护 + DSH ctx.browser provider + 兼容 dsh-univer-office 的可执行包装（非 root 服务器环境）
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), 1 of them reconstructed (hollow dots); sampled points, not a daily series
10-05 → 11-09 · 6 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-12 → 11-09 · 5 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-28 → 11-09 · 40 points
The snapshot’s last-week rolling window (official npm + npmmirror combined)
09-28 → 11-11 · 41 points
Installation
dsh plugin --profile web add dsh-browser-serviceInstall method: npm · runtime verified (L5)
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.2-rc.1 current | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 |
|---|---|---|---|---|---|
| 0.8.3 | ✓ | ✓ | ✓ | ✓ | ✓ |
| 0.8.2 | · | · | · | · | · |
| 0.8.1 | · | · | · | · | · |
| 0.8.0 | · | · | · | · | · |
| 0.7.0 | · | · | · | · | · |
0.8.3npm✓ 8 runtime-verified2026-11-05
dsh-browser-service
✓dsh 0.2.2-rc.1current2026-11-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · dsh-browser-service@0.8.3
ID: dsh-browser-service@0.8.3@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
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-11-01L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · dsh-browser-service@0.8.3
ID: dsh-browser-service@0.8.3@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
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-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-browser-service@0.8.3
ID: dsh-browser-service@0.8.3@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
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-browser-service@0.8.3
ID: dsh-browser-service@0.8.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-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-browser-service@0.8.3
ID: dsh-browser-service@0.8.3@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-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.
✓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-service@0.8.3
ID: dsh-browser-service@0.8.3@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-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.2.0-rc.22026-10-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-browser-service@0.8.3
ID: dsh-browser-service@0.8.3@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-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.
✓prehistory2026-10-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-browser-service@0.8.3
ID: dsh-browser-service@0.8.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.
0.8.2npm2026-10-04
dsh-browser-service
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.8.1npm✓ 1 runtime-verified2026-10-03
dsh-browser-service
✓prehistory2026-10-03L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-browser-service@0.8.1
ID: dsh-browser-service@0.8.1@dshunknown · profile: l4-sandbox
Issued: 2026-10-03 · expires: 2026-10-10
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.
0.8.0npm✓ 1 runtime-verified2026-10-01
dsh-browser-service
✓prehistory2026-10-01L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-browser-service@0.8.0
ID: dsh-browser-service@0.8.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-01 · expires: 2026-10-08
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.
0.7.0npm✓ 1 runtime-verified2026-09-30
dsh-browser-service
✓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-service@0.7.0
ID: dsh-browser-service@0.7.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-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.
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-service/?ref=badge)``[](https://www.dsh.so/artifact/dsh-browser-service/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-browser-service/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-browser-service/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-browser-service/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-browser-service/?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.8.3dsh manifest0.8.3npm2026-11-110.8.3same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (4)
- warningnetIp · network
scripts/lib/matrix-probe.mjs:57cdpUrl: `http://127.0.0.1:${port}`, - warningchildProcess · code-exec
src/daemon.mjs:156const child = spawn(cfg.kernel, args, { stdio: ['ignore', out, out], env: process.env }); - warningnetIp · network
src/daemon.mjs:17const res = await fetch(`http://127.0.0.1:${port}/json/version`, { - warningnetIp · network
tools/seam-probe/index.js:13const TARGET_URL = process.env.M2_PROBE_URL || 'http://127.0.0.1:9413/';
show 4 audit findings
- mediumHeadless Chromium is always launched with --no-sandbox, so untrusted page content runs at full process privilege
src/config.mjs:127Every kernel started by the supervisor gets --no-sandbox unconditionally (same in skills/browser-runtime/scripts/chromium-wrapper.sh), and the browser_* tool surface lets the model navigate to arbitrary URLs, including ones an attacker influences via prompt injection. A renderer compromise then runs with the DSH user's full privileges instead of being contained by the OS sandbox (read ~/.dsh, tokens, network).
- lowdshBin interpolated into `sh -c` command string in the peer-linking helper
scripts/lib/host-peers.mjs:19Callers that pass an attacker-influenced dshBin (e.g. a CLI option or env value forwarded by the matrix script) get shell metacharacter execution. The default value is 'dsh' and the file is a dev/verification helper, so no runtime-reachable path was demonstrated.
- lowBrowser kernel path from config.json/env is spawned after an executable check only
src/config.mjs:96assertKernelExecutable only verifies exists/file/X_OK, so anyone able to write $DSH_HOME/browser-service/config.json (or set DSH_BROWSER_CHROME/DSH_BROWSER_WRAPPER) can make the daemon spawn an arbitrary binary with the user's privileges. This is intended configuration surface, and write access to that 0700 root already implies code execution as the user, so impact is limited.
- lowDiagnostic probe appends to a fixed /tmp path with default permissions
tools/seam-probe/index.js:16If this diagnostic plugin is loaded, page URLs/titles/snapshots are written to a predictable world-readable /tmp file, and a pre-created symlink there could redirect the append to another file owned by the DSH user. It is a dev probe and no patch entry loading it was found in the harvested files.
Browser daemon in a wrapper looks well-guarded (loopback-only CDP, Bearer token, 0600 state), but the bundled kernel runs with --no-sandbox; several low-risk gaps in dev scripts.
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-10-03 · activity: Stable
• Repo created: 2026-09-26
• 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 @lyp88997/dsh-browser-service?
@lyp88997/dsh-browser-service 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 @lyp88997/dsh-browser-service?
Run dsh plugin --profile web add dsh-browser-service 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-11 (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.