Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
Data as of (UTC)
What it doesAI
Unofficial macOS port of the SurfCore DSH QQ bot, shipping patches, installer scripts and setup docs (no bundled QQ/NapCat binaries).
- Unofficial macOS port of the SurfCore DSH QQ bot
- Includes patches, installer scripts and documentation
- Ships no QQ/NapCat binaries or account data
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:Shaoji-Lumine/macos-dsh-qq-bot#v0.1.16Install method: GitHub · runtime test inconclusive (L5 unknown)
Verification & Compatibility○ Ecosystem plugin
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.2-rc.1 current |
|---|---|
| v0.1.16 | ○ |
v0.1.16github○ 1 ecosystem plugin2026-11-11
https://github.com/Shaoji-Lumine/macos-dsh-qq-bot
○dsh 0.2.2-rc.1current2026-11-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/Shaoji-Lumine/macos-dsh-qq-bot#v0.1.16
ID: macos-dsh-qq-bot@v0.1.16@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-11 · expires: 2026-11-18
View checks & evidence
not present in web-profile loader inventory
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/macos-dsh-qq-bot/?ref=badge)`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.16git2026-11-11v0.1.16same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (6)
- criticaldestructiveRm · destructive
scripts/setup-napcat.sh:35rm -rf /tmp/napcat-installer && mkdir -p /tmp/napcat-installer - warningnetIp · network
scripts/install.sh:130curl -sS -X POST -H "x-console-token: \$TOKEN" http://127.0.0.1:3100/api/stop >/dev/null 2>&1 || true - warningcurlDownload · network
scripts/setup-napcat.sh:32curl -fL --retry 3 -o "$ZIP" "$ASSET_URL" - warningnetIp · network
scripts/start-surfcore.sh:50say "✅ SurfCore 已启动：http://127.0.0.1:3100" - warningnetIp · network
scripts/start-surfcore.sh:51say " 查看状态：curl -H \"x-console-token: \$(cat $SURFCORE_DIR/config.json | grep consoleToken | cut -d'\"' -f4)\" http://127.0.0.1:3100/api/s - warningnetIp · network
scripts/uninstall.sh:14[ -n "$TOKEN" ] && curl -sS -X POST -H "x-console-token: $TOKEN" http://127.0.0.1:3100/api/stop >/dev/null 2>&1 || true
show 4 audit findings
- mediumPersistent LaunchAgent silently rewrites DSH host config (openBrowser) outside the plugin directory
scripts/dsh-fence-guard.sh:34install-fence-guard.sh installs this script as LaunchAgent com.surfcore.dsh-fence, invoked on file change and at least every minute. It forces openBrowser: true in ~/.dsh/profiles/desktop/cordis.patch.yml and setup-dsh-plugin.sh sets networkExposure=loopback. This overrides the DSH host's own security setting without ongoing user consent, persists after the plugin is removed unless the agent is booted out, and tampers with another application's configuration.
- mediumNapCat installer downloaded from GitHub releases with no checksum/signature check, then opened
scripts/setup-napcat.sh:32The asset URL for the latest NapCat-Mac-Installer release is resolved dynamically from the GitHub API, downloaded without any hash or code-signature verification, unzipped to /tmp/napcat-installer, and the contained .app is executed via `open "$APP"`. If the upstream account/release is compromised, arbitrary code runs on the user's machine.
- lowThird-party repo cloned and npm install run; pinned-ref checkout failure silently falls back to default branch
scripts/install.sh:58install.sh clones https://github.com/Mieksido/surfcore.git and later runs `npm install --no-audit --no-fund`, executing any lifecycle scripts from that repo. Line 63 `git checkout "$SURFCORE_REF" ... || say "警告..."` means if checking out the pinned commit 0deb826 fails, the install continues on whatever branch was cloned, so executed code may not be the intended revision. Requires the user to run the installer.
- lowQQ client launched with --no-sandbox (Chromium sandbox disabled)
scripts/start-surfcore.sh:33The network-facing Tencent QQ client, which is patched with NapCat, is started with its Chromium sandbox disabled. This is required by the upstream NapCat flow but weakens process isolation and defence in depth on the host.
No exfiltration, but a persistent LaunchAgent rewrites DSH host config, an unverified remote NapCat .app is downloaded/opened, and QQ runs with --no-sandbox.
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-09 · activity: Active
• Repo created: 2026-11-04
• 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).
Frequently asked questions
What is @Shaoji-Lumine/macos-dsh-qq-bot?
@Shaoji-Lumine/macos-dsh-qq-bot is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
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 @Shaoji-Lumine/macos-dsh-qq-bot?
Run dsh plugin --profile web add github:Shaoji-Lumine/macos-dsh-qq-bot#v0.1.16 in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs.
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-11 (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.