Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
DeepSeek Harness subagent provider that delegates reasoning to Tabbit-served models through a local OpenAI-compatible gateway.
- Registers a subagent provider for DeepSeek Harness
- Routes reasoning to Tabbit models via a local gateway
- Ships a minimal preset, gateway management, and delegation guidance
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:wbdxy/dsh-tabbit-brain#v0.10.0Install method: GitHub · 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
○ 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 | dsh 0.2.1-alpha.2 |
|---|---|---|---|
| v0.10.0 | ✗ | ✗ | ✗ |
v0.10.0github3 failed2026-10-18
https://github.com/wbdxy/dsh-tabbit-brain
✗dsh 0.2.1-rc.2current2026-10-18L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/wbdxy/dsh-tabbit-brain#v0.10.0
ID: dsh-tabbit-brain@v0.10.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/wbdxy/dsh-tabbit-brain#v0.10.0
ID: dsh-tabbit-brain@v0.10.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
View checks & evidence
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-15L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/wbdxy/dsh-tabbit-brain#v0.10.0
ID: dsh-tabbit-brain@v0.10.0@dsh0.2.1-alpha.2 · profile: l3-fullscan
Issued: 2026-10-15 · expires: 2026-10-22
View checks & evidence
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-tabbit-brain/)`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.10.0dsh manifestv0.10.0git2026-10-21v0.10.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (8)
- warningnetIp · network
gateway-patch/files/scripts/lib/cdp.mjs:129const res = await fetch(`http://127.0.0.1:${port}/json/version`, { - warningnetIp · network
gateway-patch/files/scripts/lib/cdp.mjs:193const version = await (await fetch(`http://127.0.0.1:${port}/json/version`)).json(); - warningshellExec · shell
gateway-patch/install.mjs:105execFileSync('git', ['-C', DIR, 'pull', '--ff-only'], { stdio: 'inherit', timeout: 120000 }); - warningshellExec · shell
gateway-patch/install.mjs:119execFileSync('git', argv, { stdio: 'inherit', timeout: 300000 }); - warningchildProcess · code-exec
lib/index.js:238const child = spawn(opts.gatewayStartCommand, { - warningnetIp · network
lib/index.js:114gatewayUrl: z.string().default('http://127.0.0.1:8787'), - warningnetIp · network
scripts/setup.mjs:60hint: '默认 http://127.0.0.1:8787/v1', - warningnetIp · network
scripts/setup.mjs:61default: 'http://127.0.0.1:8787/v1',
show 5 audit findings
- mediumBundled gateway allows any visited website to drive the user's Tabbit session (wildcard CORS + public default key)
gateway-patch/files/src/server.mjs:181When the gateway runs (the shipped cordis.patch.yml sets gatewayAutoStart: true), any web page the user visits can POST to http://127.0.0.1:8787/v1/chat/completions; the OPTIONS handler accepts Content-Type/Authorization and every JSON response carries ACAO '*' plus the same in the OPTIONS handler. Because the installer's default key is the public, documented string sk-tabbit-local and `checkAuth` returns true when apiKey is empty, a malicious page can read replies generated with the user's logged-in Tabbit cookie: quota abuse and attacker-controlled prompts written into the user's Tabbit sess
- mediumEphemeral cookie fetch force-kills every Tabbit process, including the user's running browser
gateway-patch/files/scripts/lib/cdp.mjs:278`killIt()` runs in a finally block and targets every PID returned by tasklist for those image names, not the child it spawned; killProcessTree issues `taskkill /PID <id> /T /F`. The headless instance is started with the *real* user-data-dir, so when the user's browser is already open without a debug port (the common case this path is meant to fix) Chromium hands off to the existing instance, the fetch fails, and the finally-block terminates the user's live browser window (unsaved tabs/forms).
- lowGateway auto-start executes a configured string through a shell in the DSH process
lib/index.js:237Any value of gatewayStartCommand (deployment baseline config or the tabbit-brain settings section) is passed to /bin/sh or cmd.exe verbatim; whoever can edit those config surfaces — or a package that writes to them — gets command execution inside the DSH host. The default value shipped in cordis.patch.yml is a plain `node "src\server.mjs"`, so this is a configuration-controlled capability rather than an externally reachable one.
- lowTabbit session cookie is written back to .env in plaintext and the real profile is exposed over an unauthenticated debug port
gateway-patch/files/src/server.mjs:132The refreshed login cookie (including the HttpOnly token) is persisted unencrypted into the gateway .env on every refresh, and the same flow launches the user's real Chromium profile with `--remote-debugging-port=9222` (cdp.mjs) and `--user-data-dir=<real User Data>`, so any local process that reaches 127.0.0.1:9222 while the short-lived instance is alive can read the whole profile's cookies; the API-key slice and signKey prefix are also echoed by /healthz.
- lowInstaller pulls unpinned upstream code that the plugin can auto-execute
gateway-patch/install.mjs:24install.mjs clones the third-party repo with `--depth 1` (no pinned ref) and on every re-run does `git pull --ff-only`, with no license and no integrity check, then copies patch files over it; the shipped cordis.patch.yml is configured to start `node "src\server.mjs"` from that directory, so unreviewed upstream commits flow into code the plugin launches.
Plugin core is a subagent provider, but the bundled gateway exposes a wildcard-CORS localhost proxy with a public default key and force-kills the user's Tabbit browser.
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-07 · activity: Active
• Repo created: 2026-10-05
• Stars: ★ 1 · 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).
