Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.3 · last checked Install verification details →
Showing badges for the 5 most recent dsh versions; older ones are hidden.
What it doesAI
WeChat iLink channel and session bridge for DeepSeek Harness, with encrypted file delivery and a control CLI.
- WeChat iLink channel for DSH
- Bridges DSH sessions with WeChat
- Encrypted file delivery plus control CLI
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:LZG3530606141/dsh-wechat-bridge#v0.1.0Install 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.
Footnote: the author also wrote engines.dsh = ">=0.1.5-rc.1 <0.2.0" — DSH does not read that field (not part of the verdict).
| plugin ＼ dsh | dsh 0.2.1-rc.3 current | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 |
|---|---|---|---|---|---|
| v0.1.0 | ✓ | ✓ | ✓ | ✓ | ✓ |
v0.1.0github✓ 12 runtime-verified2026-10-26
https://github.com/LZG3530606141/dsh-wechat-bridge
✓dsh 0.2.1-rc.3current2026-10-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/LZG3530606141/dsh-wechat-bridge#v0.1.0
ID: dsh-wechat-bridge-5@v0.1.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
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.
✓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/LZG3530606141/dsh-wechat-bridge#v0.1.0
ID: dsh-wechat-bridge-5@v0.1.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
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.
✓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/LZG3530606141/dsh-wechat-bridge#v0.1.0
ID: dsh-wechat-bridge-5@v0.1.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
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.
✓dsh 0.2.1-alpha.22026-10-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/LZG3530606141/dsh-wechat-bridge#v0.1.0
ID: dsh-wechat-bridge-5@v0.1.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
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.
✓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/LZG3530606141/dsh-wechat-bridge#v0.1.0
ID: dsh-wechat-bridge-5@v0.1.0@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.
✓dsh 0.2.0-rc.12026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/LZG3530606141/dsh-wechat-bridge#v0.1.0
ID: dsh-wechat-bridge-5@v0.1.0@dsh0.2.0-rc.1 · profile: l4-sandbox
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.
✓dsh 0.1.7-rc.22026-09-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/LZG3530606141/dsh-wechat-bridge#v0.1.0
ID: dsh-wechat-bridge-5@v0.1.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
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.
✓dsh 0.1.7-alpha.22026-09-23L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/LZG3530606141/dsh-wechat-bridge#v0.1.0
ID: dsh-wechat-bridge-5@v0.1.0@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
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.
✓dsh 0.1.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/LZG3530606141/dsh-wechat-bridge#v0.1.0
ID: dsh-wechat-bridge-5@v0.1.0@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
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.
✓dsh 0.1.6-alpha.12026-09-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/LZG3530606141/dsh-wechat-bridge#v0.1.0
ID: dsh-wechat-bridge-5@v0.1.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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.
✓dsh 0.1.5-rc.22026-09-13L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/LZG3530606141/dsh-wechat-bridge#v0.1.0
ID: dsh-wechat-bridge-5@v0.1.0@dsh0.1.5-rc.2 · profile: l3-fullscan
Issued: 2026-09-13 · expires: 2026-09-20
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-10-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/LZG3530606141/dsh-wechat-bridge#v0.1.0
ID: dsh-wechat-bridge-5@v0.1.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
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 official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-wechat-bridge-5/)``[](https://www.dsh.so/artifact/dsh-wechat-bridge-5/)``[](https://www.dsh.so/artifact/dsh-wechat-bridge-5/)``[](https://www.dsh.so/artifact/dsh-wechat-bridge-5/)``[](https://www.dsh.so/artifact/dsh-wechat-bridge-5/)``[](https://www.dsh.so/artifact/dsh-wechat-bridge-5/)`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 high (authoritative when present) → overall high.
v0.1.0dsh manifestv0.1.0git2026-10-28v0.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (9)
- criticalspawnShell · shell
bin/dsh-wechat.mjs:280child = spawn(command, { shell: true, env: Object.assign({}, process.env, eventEnv), stdio: ['ignore', replyBack ? 'pipe' : 'inherit', 'pipe - warningnetIp · network
bin/dsh-wechat.mjs:88return 'http://127.0.0.1:' + port; - warningnetIp · network
bin/dsh-wechat.mjs:486const res = await fetch('http://127.0.0.1:' + state.guiPort + '/', { signal: AbortSignal.timeout(4000) }); - warningnetIp · network
src/index.mjs:411const tokenUrl = conn.authenticatedUrl('http://127.0.0.1:' + cfg.guiPort + '/'); - warningnetIp · network
src/index.mjs:421const base = 'http://127.0.0.1:' + cfg.guiPort + '/api/' + endpoint; - warningnetIp · network
src/index.mjs:1520log('CLI 控制面已就绪: http://127.0.0.1:' + cfg.port + '/api/bridge · relay=' + relayMode); - warningfsWrite · files
src/index.mjs:271try { fs.appendFileSync(LOG_FILE, text + '\n'); } catch { /* best effort */ } - warningfsWrite · files
src/index.mjs:311try { fs.writeFileSync(RELAY_FILE, mode); } catch { /* best effort */ } - warningfsWrite · files
src/index.mjs:525try { fs.writeFileSync(SEEN_FILE, JSON.stringify([...seen])); } catch { /* best effort */ }
show 4 audit findings
- highUnauthenticated /api/chat drives the local DSH agent from any reachable client
src/index.mjs:1517This route never calls control() (every sibling route such as /api/send starts with "if (!control()) return;"). It feeds attacker text straight into runChat -> guiRpc('session.prompt') / agent.followup, i.e. into the user's DSH agent, which has shell/file tool access. Anyone on the LAN when host is set to 0.0.0.0 (a documented usage) can run arbitrary prompts; even with the default 127.0.0.1 binding, a visited web page can issue a no-preflight cross-site POST (text/plain body, no Origin check) and silently drive the agent, e.g. to exfiltrate local files via the agent's own tools.
- mediumUnauthenticated /api/history and /api/status expose full conversation content
src/index.mjs:1470Neither /api/history nor /api/status calls control(); they return historyMessages(agent.session, limit) and session titles/IDs to any client that can reach the port, including a cross-site GET from a visited web page. Conversation transcripts typically contain source code, paths and other sensitive data. The same open surface also exposes /api/bridge-equivalent state indirectly via the page.
- mediumUnauthenticated state-changing endpoints can be triggered cross-site
src/index.mjs:1489/api/wechat-relogin and /api/new-session bypass control(): any reachable client (or a cross-site form/fetch with a text/plain body, no Origin check) can wipe the stored WeChat credential, force the channel offline until a physical re-scan of the QR code, and create new DSH sessions using the operator's cwd/preset.
- lowWeChat bot token and context token are stored as plaintext files with default permissions
src/index.mjs:596The WeChat bot bearer token (and, in wechat-context.txt, the conversation context token) is written unencrypted under ~/.dsh/wechat-bridge with the process umask; on a typical 022 umask any other local user can read the credential and act as the bot. The file is only removed on relogin, never expired.
Unauthenticated /api/chat and /api/history on the bridge HTTP server let any LAN peer, or a browser cross-site request, drive the local DSH agent and read its history.
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-09-12 · activity: Stable
• Repo created: 2026-09-12
• Stars: ★ 0 · Forks: 0
• Health: Stable — committed within 90 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).