Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it does
把本机已登录的豆包工作(DoubaoWork)客户端接入 DeepSeek Harness:通过客户端 DevTools 端点复用登录态调用 /chat/completion,并在输入框显示 5 小时 / 7 天额度。
Installation
dsh plugin --profile web add dsh-doubao-work-connectInstall method: npm · sandbox install ok, web smoke failed (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
package manifest not collected — the declared range is unknown.
| plugin \ dsh | dsh 0.2.1-rc.2 current |
|---|---|
| 0.1.3 | ✗ |
0.1.3npm1 failed2026-10-21
dsh-doubao-work-connect
✗dsh 0.2.1-rc.2current2026-10-21L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-doubao-work-connect@0.1.3
ID: dsh-doubao-work-connect@0.1.3@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-21 · expires: 2026-10-28
View checks & evidence
↳ carried from earlier record dsh-doubao-work-connect@dd7764@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-doubao-work-connect@dd7764@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-doubao-work-connect@dd7764@dsh0.2.1-rc.2 (l3-fullscan)
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 official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-doubao-work-connect/)`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 no conclusion — stricter wins → overall low.
v0.1.7dsh manifest0.1.7npm2026-10-210.1.7same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (9)
- warningchildProcess · code-exec
credentials.js:212const child = spawn(exe, [`--remote-debugging-port=${this.debugPort}`], { detached: true, stdio: "ignore", windowsHide: true }); - warningshellExec · shell
credentials.js:75execFile("tasklist", ["/FI", `IMAGENAME eq ${APP_PROCESS_IMAGE}`, "/FO", "CSV", "/NH"], { windowsHide: true }, (error, stdout) => { - warningshellExec · shell
credentials.js:88execFile("taskkill", ["/IM", APP_PROCESS_IMAGE, "/F"], { windowsHide: true }, () => resolve()); - warningnetIp · network
credentials.js:117const response = await fetch(`http://127.0.0.1:${port}/json/version`, { signal: AbortSignal.timeout(3000) }); - warningnetIp · network
credentials.js:181const response = await fetch(`http://127.0.0.1:${this.debugPort}/json/version`, { signal: AbortSignal.timeout(1500) }); - warningnetIp · network
credentials.js:231const list = await (await fetch(`http://127.0.0.1:${this.debugPort}/json/list`, { signal: AbortSignal.timeout(4000) })).json(); - warningnetIp · network
quota-route.js:95const url = new URL(req.url ?? "/", "http://127.0.0.1"); - warningnetIp · network
shim.js:61const url = new URL(req.url ?? "/", "http://127.0.0.1").pathname; - warningnetIp · network
shim.js:386baseUrl: () => (address === undefined ? "" : `http://127.0.0.1:${address.port}`),
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-10-21 · activity: Active
• Repo created: 2026-10-19
• Stars: ★ 2 · 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).
