⚠️ This repository has been renamed: zhy5/dsh-wx-bridge — click to visit the new location. Everything below is preserved as originally indexed.
Install verification: runtime verified (L5) · tested on dsh 0.2.0-rc.2 · last checked Install verification details →
Data as of (UTC)
What it doesAI
DSH plugin that bridges WeChat (official iLink/ClawBot) to DeepSeek Harness with a live status settings panel and bundled bridge/keeper kernel.
- Connects WeChat via official iLink/ClawBot to DeepSeek Harness
- Live status settings panel for the WeChat bridge
- Ships a bundled bridge/keeper kernel out of the box
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.
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); the npm pair from every snapshot.
5 samples (roughly every 1 days), 5 of them reconstructed (hollow dots); sampled points, not a daily series
09-21 → 10-04 · 5 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
09-28 → 10-04 · 4 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
The snapshot’s last-week rolling window (official npm + npmmirror combined)
Only 0 points (< 3): no chart yet
no data yet
Installation
dsh plugin --profile web add github:zhy5/wxbridge#v1.1.8Install method: GitHub · runtime verified (L5) · verified on dsh 0.2.0-rc.2
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.0-rc.2 | dsh 0.1.7-rc.2 | dsh 0.1.7-rc.1 | dsh 0.1.6-alpha.2 | prehistory |
|---|---|---|---|---|---|
| v1.1.8 | ✓ | · | · | · | ✓ |
v1.1.8github✓ 2 runtime-verified2026-10-09
https://github.com/zhy5/wxbridge
✓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/zhy5/wxbridge#v1.1.8
ID: wxbridge@v1.1.8@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
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.
✓prehistory2026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/zhy5/wxbridge#v1.1.8
ID: wxbridge@v1.1.8@dshunknown · profile: l3-fullscan
Issued: 2026-09-30 · expires: 2026-10-07
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.
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 dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/wxbridge/?ref=badge)``[](https://www.dsh.so/artifact/wxbridge/?ref=badge-install)``[](https://www.dsh.so/artifact/wxbridge/?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.
v1.1.8dsh manifestv1.1.8git2026-10-08v1.1.8same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (9)
- warningchildProcess · code-exec
lib/kernel/acp-preset-shim.mjs:177const r = spawnSync(process.execPath, ['--check', tmp], { timeout: 30000, windowsHide: true }) - warningchildProcess · code-exec
lib/kernel/acp.mjs:88const child = spawn(this.node, args, { cwd: this.cwd, windowsHide: true, stdio: ['pipe', 'pipe', 'pipe'], env }) - warningchildProcess · code-exec
lib/kernel/bridge.mjs:309try { spawn('cmd.exe', ['/c', 'icacls "' + AUTH_FILE + '" /inheritance:r /grant:r "' + process.env.USERNAME + ':R"'], { windowsHide: true, s - warningchildProcess · code-exec
lib/kernel/bridge.mjs:424try { spawn('cmd.exe', ['/c', 'icacls "' + target + '" /inheritance:r /grant:r "' + process.env.USERNAME + ':R"'], { windowsHide: true, stdi - warningchildProcess · code-exec
lib/kernel/bridge.mjs:1431function killTree(pid) { try { spawn('taskkill', ['/PID', String(pid), '/T', '/F'], { windowsHide: true, stdio: 'ignore' }) } catch {} } - warningshellExec · shell
lib/kernel/bridge.mjs:80const raw = execFileSync('powershell.exe', ['-NoProfile', '-Command', ps], { encoding: 'utf8', windowsHide: true, timeout: 20000 }) - warningshellExec · shell
lib/kernel/bridge.mjs:2185execFileSync(NODE_BIN, [helper, '--text', '自测推送：来自 wxpush', '--data-dir', tmp], { stdio: 'ignore' }) - warningnetIp · network
lib/kernel/bridge.mjs:775const r = await fetch('http://127.0.0.1:' + port + '/wxbridge/task', { - warningnetIp · network
lib/kernel/bridge.mjs:1274const r = await fetch('http://127.0.0.1:' + port + '/wxbridge/attach', {
show 5 audit findings
- mediumAt runtime the plugin patches source inside the installed @deepseek-ai/dsh-acp package, outside its own directory
lib/kernel/acp-preset-shim.mjs:186ensureAcpPresetSupport() edits a hard-coded 5-anchor patch into another installed package's lib/index.js, which the host then executes. The only guards are exact-string anchor matches and `node --check`; the target path comes from runtime discovery (env/args, host-runtime.json, PATH, Program Files scan, WMI), so any path that resolves as the DSH runtime can be rewritten. It runs on startup whenever a preset overlay is generated, i.e. also triggered by an allow-listed user sending /预设.
- lowAttachment download fetches a URL taken verbatim from the inbound message, without a host allow-list
lib/kernel/bridge.mjsmedia.full_url / node.url from the message wins over the CDN URL, so an allow-listed sender can point the fetch at 127.0.0.1 or an internal host and have the response written into the media directory. Auth is checked first, so with the default 'strict' allowlist a stranger cannot reach it.
- lowWindows ACL command is built by string concatenation from env and path values
lib/kernel/bridge.mjscmd.exe parses one string, so a double quote or `&` inside USERNAME or inside the data-dir path (both locally controlled via env/args) breaks out of the quoted argument. The same pattern is repeated in prepareChildHome for the child .credentials.yaml. Precondition is same-user control of env/config, so this is a hardening gap rather than a remote vector.
- lowHost .credentials.yaml is rewritten and all discovered API keys are copied in plaintext into the plugin data dir
lib/kernel/bridge.mjsIn shared (HOST_HOME) mode the bridge regenerates the host's credentials file from a simplified `refs:` parse, so comments or any non-refs field in that user-owned file are dropped. In all modes it aggregates keys from DSH_HOME/HOST_HOME/CHILD_HOME into <dataDir>/dsh-home/.credentials.yaml in plaintext, protected only by an icacls call on Windows.
- lowUnauthenticated local outbox lets any process on the machine send WeChat messages as the bot
lib/kernel/bridge.mjsAny process that can create <dataDir>/outbox/*.json makes the bridge (which holds the WeChat token) deliver its text, with no signature or token on the entry; only the recipient is constrained to state.allowedUsers. Similar trust is placed in the loopback /wxbridge/task and /wxbridge/attach endpoints (no auth beyond 127.0.0.1).
No remote code-execution path: spawns use argv arrays, allowlist defaults to strict, approvals fail closed; main residual risk is the runtime write into the installed dsh-acp package.
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-10-23 · activity: Active
• Repo created: 2026-09-21
• Stars: ★ 5 · Forks: 1
• Health: Active — committed within last 30 days
Source
GitHub: github.com/zhy5/wxbridge
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 @zhy5/wxbridge?
@zhy5/wxbridge 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 @zhy5/wxbridge?
Run dsh plugin --profile web add github:zhy5/wxbridge#v1.1.8 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-10-25 (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.