leonathan369-droid/qq-bridge
C3QQ Bridge for macOS —— DeepSeek Harness QQ 集成:DSH 设置页控制中心(真实健康检查 / 一键启停 / 运行模式 / QQ 专用模型与推理强度)+ LLBot 适配。上游 Derpyu520/qq-bridge 的衍生版(MIT)。
★ 0 · leonathan369-droid/qq-bridge source on GitHub · this plugin in the registry
leonathan369-droid/qq-bridge is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, runs code at install time, can spawn subprocesses, executes system commands.
Installable plugin — declares a dsh.bundle manifest
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ['./presets/qq-chat.patch.yml', './presets/qq-chat-v2.patch.yml'] |
| runs code at install time | install_script | postinstall: node scripts/patch-snowluma-sdk.mjs |
| can spawn subprocesses | subprocess_service | inject: subprocess |
| executes system commands | exec | ×61 in authored code, e.g. scripts/audit-bridge-harness.mjs:9, scripts/audit-bridge-harness.mjs:9 |
| uses eval / new Function | eval | ×4 in authored code, e.g. scripts/test-console-static.mjs:46, scripts/test-console-static.mjs:67 |
| decodes base64 payloads | base64_decode | ×1 in authored code, e.g. src/bridge.js:7926 |
| starts a network server | net_server | ×14 in authored code, e.g. scripts/console-ui-fixture.mjs:347, scripts/test-bridge-ws-recovery.mjs:33 |
| reads credential-class env vars | token_env | DSH_LAUNCH_TOKEN, DSH_PROBE_COOKIE, QQ_CONSOLE_TOKEN, SNOWLUMA_TOKEN |
Tool registrations
0 static tool registration point(s).
Services it injects
settings slots subprocess tools webServer
Hooks it attaches
tools/change
Outbound domains
x.com dsh.example.com mobile.moegirl.org.cn evil.com evil.example.com www.bing.com www.so.com
Environment variables it reads
DSH_HOME DSH_BASE_URL QQ_BRIDGE_TEST_LIVE USERPROFILE FFPROBE_PATH QQ_BRIDGE_PRIVACY_DEBUG ComSpec TEMP FFMPEG_PATH SNOWLUMA_HOME
How to read this
Levels measure capability surface and transparency, not maliciousness. A C3 plugin can be entirely legitimate — a desktop shell genuinely needs subprocesses. The point is that you can see this before installing. See the levels explained and how dsh plugins work.
Findings come from static analysis of shipped code; nothing is executed. Think a flag is wrong? Open an issue — every flag cites the file and line it came from.