dsh-browser-use avatar

dsh-browser-use

为 DeepSeek Harness (DSH) 插件生态打造的浏览器自动化插件

PluginBrowserAutomationWeb search
Verification
L3 · Install spec
stale
Risk
LowRisk
Health
Stable
Trust
Silver

Install verification: sandbox install failed (L4) · tested on dsh 0.1.7-rc.2 · last checked Install verification details →

What it doesAI

Provides browser automation for DSH, with layered packages for Hubs, backends, and domains that publish browser tools.

  • Three-layer architecture: Hub, Backend, Domain
  • Named browser registry and backend contracts
  • Publishes browser tools and settings to DSH
browserAI

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:helloproblems/dsh-browser-use#0.7.0

security scan passed · source release 0.7.0

Install method: GitHub · sandbox install failed (L4) · verified on dsh 0.1.7-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

Declared DSH compatibilityfrom package.json · peerDependencies
only dsh 0.1.6-alpha.1 (this exact version)

Based on 1 requirement(s) across 1 @deepseek-ai/dsh-* packages.

raw ranges0.1.6-alpha.1 ×1

✗ Running dsh 0.2.1-rc.2 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-use-2@0.7.0 0.2.1-rc.2 (the exemption lives in the local profile; this site does not assume one)

Whether it actually runs is a separate question → see the measured matrix below (L1–L5).

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)
At-a-glance → evidence in the cards below
plugin \ dshdsh 0.1.7-rc.2dsh 0.1.7-rc.1dsh 0.1.7-alpha.2dsh 0.1.6-alpha.2dsh 0.1.6-alpha.1
0.7.0·····
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
0.7.0github2026-10-18

https://github.com/helloproblems/dsh-browser-use

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

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 official badges in your README to showcase security & install-test status:

dsh.so risk
`[![dsh.so risk](https://www.dsh.so/badge/dsh-browser-use-2.svg)](https://www.dsh.so/artifact/dsh-browser-use-2/)`

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.

dsh-browser-use-2Automated review · daily

Static low, dynamic no conclusion — stricter wins → overall low.

static low→dynamic no conclusion→overall low
0 critical·0 high
lowoverall · low
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
plugin versionv0.7.0dsh manifest
scanned version0.7.0git2026-10-21
current version0.7.0same version
vet verdictclean · git

Vet is an AST static scan (npm artifact or git source).

2model reads redacted source context · never executes plugin code

not in the dynamic queue (queue only covers plugins static-flagged at warn or above) — this does not mean the dynamic audit found it safe.

Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.

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-16 · activity: Stable

• Repo created: 2026-09-03

• Stars: ★ 1 · Forks: 0

• Health: Stable — committed within 90 days

Source

GitHub: github.com/helloproblems/dsh-browser-use

Was this page helpful?