Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it does
在 DeepSeek Harness (DSH) 桌面端用网页版 DeepSeek 账号做联网搜索——web_search provider backed by chat.deepseek.com, no API key needed
Installation
dsh plugin --profile web add github:1parado/dsh-deepseek-web-searchInstall method: GitHub · 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.1-rc.2 current | dsh 0.2.1-alpha.4 |
|---|---|---|
| 105367 | ✓ | ✓ |
105367github✓ 2 runtime-verified2026-10-18
https://github.com/1parado/dsh-deepseek-web-search
✓dsh 0.2.1-rc.2current2026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/1parado/dsh-deepseek-web-search (version unstated)
ID: dsh-deepseek-web-search@105367@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
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-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/1parado/dsh-deepseek-web-search (version unstated)
ID: dsh-deepseek-web-search@105367@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-deepseek-web-search/)``[](https://www.dsh.so/artifact/dsh-deepseek-web-search/)`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 — stricter wins → overall medium.
v0.3.3dsh manifest0.3.3git2026-10-210.3.3same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (12)
- criticalshellExec · shell
lib/index.js:258await execFile(command.node, ['-e', 'require("node:child_process").execSync("pnpm update dsh-deepseek-web-search", {stdio:"inherit"})'], { c - warningchildProcess · code-exec
lib/browser-login.js:378const child = spawn(browserPath, [ - warningchildProcess · code-exec
lib/browser-login.js:496spawn('taskkill', ['/pid', String(child.pid), '/T', '/F'], { stdio: 'ignore', detached: true }).unref() - warningshellExec · shell
lib/browser-login.js:103const choice = execFileSync('reg', [ - warningshellExec · shell
lib/browser-login.js:110const command = execFileSync('reg', [ - warningshellExec · shell
lib/browser-login.js:191const output = execFileSync('reg', ['query', key, '/ve'], { encoding: 'utf8', stdio: ['ignore', 'pipe', 'ignore'] }) - warningnetIp · network
lib/browser-login.js:315const list = await fetch(`http://127.0.0.1:${port}/json/list`).then((response) => response.json()) - warningnetIp · network
lib/browser-login.js:342const response = await fetch(`http://127.0.0.1:${port}/json/version`, { signal: controller.signal }) - warningchildProcess · code-exec
lib/index.js:226const child = spawn(command, args, { ...options, stdio: ['ignore', 'pipe', 'pipe'] }) - warningchildProcess · code-exec
lib/index.js:525spawn('explorer.exe', ['/select,', file], { detached: true, stdio: 'ignore' }).unref() - warningshellExec · shell
lib/index.js:224function execFile(command, args, options) { - warningshellExec · shell
lib/index.js:255await execFile(command.node, [command.pnpmCjs, 'update', 'dsh-deepseek-web-search'], { cwd })
show 2 audit findings
- mediumSettings HTTP API has no authentication/Origin-CSRF check and exposes privileged state-changing routes
lib/index.js:162createSettingsApi's handler performs no session check, Origin/Host validation or CSRF token check; it only branches on method+path. Anything that can reach the DSH web server (a malicious local process, a cross-site auto-submitted form for the body-less routes such as /clear-login-data or /update/apply, or DNS rebinding that makes JSON POSTs same-origin) can delete the login profile, spawn explorer.exe, launch a browser, or run `pnpm update` in the profile. /browser-login/start additionally takes `body.browserPath` and passes it to child_process.spawn via findBrowser(), so a JSON-capable calle
- lowLogin flow runs Chromium with a fixed remote-debugging port, giving local processes full DevTools control
lib/browser-login.js:27During waitForToken (up to 5 minutes), a Chromium instance listens on 127.0.0.1:9223 with DevTools enabled. Any local process can connect, enumerate targets, and Runtime.evaluate arbitrary JS in the chat.deepseek.com tab of the dedicated login profile, reading the userToken (and any other storage/cookies of that profile) or driving the session. The dedicated profile and process teardown limit the blast radius, but the port is world-local and predictable while open.
Token handling is scoped to https chat.deepseek.com and logs are redacted, but the settings HTTP API lacks auth/CSRF checks and the login flow exposes a local DevTools port.
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-10-17 · activity: Active
• Repo created: 2026-10-17
• Stars: ★ 5 · Forks: 0
• Health: Active — committed within last 30 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).
