Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it does
In-process QQ official-bot bridge for DeepSeek Harness: QQ messages start or resume real DSH sessions inside the host and send the result back to QQ.
Installation
dsh plugin --profile web add github:tbb051122/dsh-plugin-qq-bridgeInstall 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 |
|---|---|
| aae281 | ✓ |
aae281github✓ 1 runtime-verified2026-10-19
https://github.com/tbb051122/dsh-plugin-qq-bridge
✓dsh 0.2.1-rc.2current2026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/tbb051122/dsh-plugin-qq-bridge (version unstated)
ID: dsh-plugin-qq-bridge@aae281@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
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-plugin-qq-bridge/)``[](https://www.dsh.so/artifact/dsh-plugin-qq-bridge/)`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.1.0dsh manifest0.1.0git2026-10-210.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (7)
- warningfsWrite · files
lib/history.mjs:26fs.appendFileSync(historyFile(cfg, key), JSON.stringify({ t: Date.now(), role, text: s, ...meta }) + '\n', 'utf8'); - warningfsWrite · files
lib/index.js:89try { fs.writeFileSync(SELFTEST_MARKER, new Date().toISOString() + '\n', 'utf8'); } catch (e) { log.warn('写自检标记失败', e); } - warningfsWrite · files
lib/qqapp.mjs:426fs.writeFileSync(dest, buf); - warningfsWrite · files
lib/state.mjs:38fs.writeFileSync(tmp, data); - warningfsWrite · files
lib/state.mjs:41try { fs.writeFileSync(file, data); return true; } catch {} - warningfsWrite · files
lib/util.mjs:14try { fs.appendFileSync(file, line + '\n'); } catch {} - warningfsWrite · files
lib/workspaces.mjs:87fs.writeFileSync(path.join(dir, '_workspaces.md'), [
show 2 audit findings
- mediumUnthrottled 6-digit bind code can be brute-forced to bypass the whitelist
lib/state.mjs:72A /bind message is processed before the allowlist check (qqapp.mjs: `const bound = cmd === 'bind'; if (!bound) { ... whitelist ... }`), and the handler compares `code !== ensureBindCode(state)` with no attempt limit, backoff, or rotation. Anyone able to message the bot (C2C or a group it joined) can try 900k codes; on success the handler pushes the sender's openid AND group_openid into state.allow, so a single lucky guess grants the whole group access to the full-access agent, i.e. host code execution.
- mediumdanger-full-access default gives any allowed user or group member unrestricted host execution
lib/config.mjs:42Every QQ-driven agent run is decorated with this preset (agent.mjs `const name = cfg.permissionPreset || 'danger-full-access'`), so no approval or sandbox stands between a QQ message and arbitrary local commands. Because isAllowed() accepts any member of a whitelisted group, adding one group to the allowlist (or a successful bind) lets all its members run commands and read/upload arbitrary local files back through the [[send-file:...]] channel in qqapp.mjs sendAttachments.
Whitelist is fail-closed, but a 6-digit unthrottled bind code can be brute-forced to gain full-access agent execution; group whitelisting extends that to every member.
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-18 · activity: Active
• Repo created: 2026-10-18
• Stars: ★ 0 · 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).
