把已存在的固定 DSH大肥鱼 会话接到 QQ(OneBot/NapCat)并保留原上下文:白名单 + @/昵称必唤醒 + 概率唤醒,其余只记录,让大肥鱼成为你的群友;也可以把 agent 扔进群里当群友玩(不建议公共群)。 / Bridge one existing DSH session to QQ via OneBot/NapCat, keeping its context — fail-closed whitelist, @/nickname wake, configurable-probability wake.
Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.1 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Bridges an existing DSH session to QQ via OneBot/NapCat, keeping context with a fail-closed whitelist and configurable wake rules.
- Connects one existing DSH session to QQ via OneBot/NapCat
- Fail-closed whitelist; @ or nickname always wakes, plus probability wake
- Non-matching messages are only logged, not answered
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:sj244/dsh-qq-bridge#v0.1.3Install method: GitHub · runtime verified (L5) · verified on dsh 0.2.2-rc.1
Trends
Four lines, four questions: total stars, stars gained this week, cumulative downloads, downloads this week. The GitHub pair comes from real-read sampling — a rotating daily shard, so one plugin is re-read roughly every 5–14 days, sparser than npm; the npm pair has a value on every snapshot day. The two cumulative panels are smoothed curves with no sample markers; the two weekly panels keep their raw bars and add a 4-week moving-average trend line that strips single-week noise down to the direction of travel.
current (registry 2026-11-15) · 7 samples (roughly every 7 days), 2 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
10-03 → 11-11 · 7 points
Bars = the delta between two samples 5–14 days apart (negative points down, faint bars contain reconstructed points); line = 4-week moving-average trend
10-14 → 11-11 · 5 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
Bars = the snapshot’s last-week rolling window (official npm + npmmirror combined); line = 4-week moving-average trend — the shape of weekly demand, not a user count
Only 0 points (< 3): no chart yet
no data yet
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
Based on 1 requirement(s) across 2 @deepseek-ai/dsh-* packages. raw ranges
* ×2
✓ Running dsh 0.2.2-rc.3 is within the declared range — install is not blocked by version.
Deciding channel: no engines.dsh declared, so every dsh* peer is checked (workspace:^ | ~ | * counts as the running version).
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| plugin \ dsh | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 |
|---|---|---|---|---|---|
| v0.1.3 | ✓ | ✓ | ✓ | ✓ | ✓ |
| v0.1.1 | · | · | · | · | · |
| v0.1.0 | · | · | · | · | · |
v0.1.3github✓ 6 runtime-verified2026-11-14
https://github.com/sj244/dsh-qq-bridge
✓dsh 0.2.2-rc.12026-11-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/sj244/dsh-qq-bridge#v0.1.3
ID: dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
View checks & evidence
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
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-rc.52026-10-31L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/sj244/dsh-qq-bridge#v0.1.3
ID: dsh-qq-bridge-3@v0.1.3@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
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-rc.32026-10-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/sj244/dsh-qq-bridge#v0.1.3
ID: dsh-qq-bridge-3@v0.1.3@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
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-rc.22026-10-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/sj244/dsh-qq-bridge#v0.1.3
ID: dsh-qq-bridge-3@v0.1.3@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
View checks & evidence
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
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/sj244/dsh-qq-bridge#v0.1.3
ID: dsh-qq-bridge-3@v0.1.3@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
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.22026-10-13L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/sj244/dsh-qq-bridge#v0.1.3
ID: dsh-qq-bridge-3@v0.1.3@dsh0.2.1-alpha.2 · profile: l3-fullscan
Issued: 2026-10-13 · expires: 2026-10-20
View checks & evidence
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.1.1github✓ 2 runtime-verified2026-10-10
https://github.com/sj244/dsh-qq-bridge
✓dsh 0.2.0-rc.22026-10-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/sj244/dsh-qq-bridge#v0.1.1
ID: dsh-qq-bridge-3@v0.1.1@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓prehistory2026-10-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/sj244/dsh-qq-bridge#v0.1.1
ID: dsh-qq-bridge-3@v0.1.1@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.1.0github✓ 1 runtime-verified2026-10-01
https://github.com/sj244/dsh-qq-bridge
✓prehistory2026-10-01L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/sj244/dsh-qq-bridge#v0.1.0
ID: dsh-qq-bridge-3@v0.1.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-01 · expires: 2026-10-08
View checks & evidence
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-qq-bridge-3@v0.1.3@dsh0.2.2-rc.3 (l3-fullscan)
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 dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/dsh-qq-bridge-3/?ref=badge)``[](https://www.dsh.so/artifact/dsh-qq-bridge-3/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-qq-bridge-3/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-qq-bridge-3/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-qq-bridge-3/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-qq-bridge-3/?ref=badge-install)`dsh.so is an independent community project, not affiliated with or endorsed by DeepSeek AI. Badges are maintained by dsh.so; embed links carry a ?ref= attribution parameter.
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 (authoritative when present) → overall medium.
v0.1.3dsh manifestv0.1.3git2026-11-15v0.1.3same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningnetIp · network
client/client.js:142{ key: 'downloadProxy', label: '下载代理', kind: 'text', hint: '下载 NapCat 用的 HTTP 代理(如 http://127.0.0.1:7890);留空 = 读环境变量。' }, - warningchildProcess · code-exec
index.js:2759const handle = subprocess.spawn({ - warningchildProcess · code-exec
index.js:2844const child = spawn(command, [installDir], { detached: true, stdio: 'ignore' }) - warningnetIp · network
index.js:136downloadProxy: Schema.string().default('').description('下载用的 HTTP 代理(如 http://127.0.0.1:7890);留空 = 读环境变量,再不行直连。'), - warningnetIp · network
index.js:175downloadProxy: Schema.string().default('').description('下载 NapCat 用的 HTTP 代理(如 http://127.0.0.1:7890);留空 = 读环境变量,再不行直连。'), - warningnetIp · network
index.js:2639downloadProxy: proxyFor(s) || '(未配置 → 直连;本机直连 GitHub 不通,建议设成 http://127.0.0.1:7890)',
show 4 audit findings
- mediumImage URLs taken from inbound OneBot events are fetched without scheme/host validation (SSRF)
index.js:1355cacheImage() is called from handleInbound() for every non-dropped message and fetches msg.images[].url, which mapOneBotMessage() copies straight out of the OneBot segment (`data.url || data.file`) or out of the CQ-code `url=`/`file=` fields. There is no allowlist of schemes/hosts and no private/loopback/link-local range check, and redirects are followed by default. Whoever can feed events into the WS connection (a compromised/spoofed OneBot side, or a peer in a whitelisted group whose client supplies an arbitrary image URL) can therefore make the DSH host issue GET requests to internal or loop
- mediumqq_bridge_napcat can download and spawn a third-party binary with no approval gate
index.js:2270The launch path spawns `cmd.exe /c <installDir>/.../launcher-win10.bat` (or NapCatWinBootMain.exe + hook DLL) through ctx.get('subprocess'), and the download path fetches and extracts a GitHub release asset into that directory. Nothing asks the human to approve: the tool is registered unconditionally and is reachable from any turn, and QQ message text is explicitly untrusted input that reaches the model, so a chat-level prompt injection can attempt to steer the model into `download`/`launch`. Integrity of the asset depends on downloadVerified()/extractZip() in napcat.js, which was not harveste
- lowFile-manager spawn uses a settings-derived path (no shell, guarded by loopback API)
index.js:2405revealNapcatDir() spawns explorer.exe / open / xdg-open with `napcatInstallDir || defaultInstallDir(home)` as a single argv element, so there is no shell interpolation and no command injection. It is only reachable through POST /api/qq-bridge/napcat/reveal, which passes the loopback + Origin/Referer + JSON content-type gate, so exploitation requires an already-local caller.
- lowNapCat WebUI token echoed to the browser by a GET route protected only by Origin/Referer
index.js:2385GET /api/qq-bridge/napcat returns the full WebUI URL including the random NapCat token. checkLocalRequest accepts requests with neither Origin nor Referer (cross-site GETs from a browser send no Origin, and the response has no CORS headers, so it cannot be read cross-origin), so this is not a demonstrated leak — but the token is emitted over plain HTTP on every card refresh, and any future addition of a CORS header or a proxying client would expose it.
Loopback API and whitelists are well-guarded, but inbound image URLs are fetched unvalidated (SSRF) and the NapCat tool downloads/spawns a binary with no approval gate.
Rule (2026-10-28): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); the static scan tier (vet primary, dsh backstop) applies only when there is none (not queued / audit failed / withdrawn). The audit never writes the exemption list (exemptions are manual only); a wrong conclusion is withdrawn by human review and the tier falls back to the static scan tier.
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-11-12 · activity: Active
• Repo created: 2026-09-29
• Stars: ★ 8 · Forks: 5
• Health: Active — committed within last 30 days
Source
GitHub: github.com/sj244/dsh-qq-bridge
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
Frequently asked questions
What is @sj244/dsh-qq-bridge?
@sj244/dsh-qq-bridge is a DeepSeek Harness (dsh) plugin listed on dsh.so — an independent community registry that indexes public source repositories and publishes automated security-scan and install-verification results for each entry.
Is dsh.so or this plugin page official?
dsh.so is an independent community registry and is not affiliated with, endorsed by, or sponsored by DeepSeek AI.
How do I install @sj244/dsh-qq-bridge?
Run dsh plugin --profile web add github:sj244/dsh-qq-bridge#v0.1.3 in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4) plus web smoke testing (L5).
How does the security scan relate to a manual audit?
Both layers are automated, not a manual audit. The static scan is heuristic analysis of the repository source, so it can produce false positives and miss context. The model-driven dynamic security audit only covers plugins static-flagged at warn or above, never executes plugin code, and its conclusion is authoritative when there is one (it may raise or lower the static tier); exemptions stay manual. Neither layer is an endorsement: review the repository and the permissions it asks for before installing, together with the verification level and health signals.
How fresh is the data on this page?
The data on this page is as of 2026-11-15 (UTC) — the most recent valid timestamp among the registry refresh, install verification, security scan and dynamic audit. Build time is never used as a data date.
