Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.2-rc.3 · last checked Install verification details →
Data as of (UTC)
What it doesAI
DSH plugin integrating WeChat ClawBot with DeepSeek Harness for chat replies and proactive notifications.
- Uses official WeChat ClawBot API
- Persistent agent sessions for WeChat
- Sends notifications and approval requests
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:MadDoooog/dsh-weixinbot#v0.1.0Install method: GitHub · sandbox install ok, web smoke failed (L5) · verified on dsh 0.2.2-rc.3
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.
7 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-13 · 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-05 → 11-13 · 3 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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.2-rc.3 | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| v0.1.0 | ✗ | ✗ | ✗ | ✗ | ✗ |
v0.1.0github16 failed2026-11-17
https://github.com/MadDoooog/dsh-weixinbot
✗dsh 0.2.2-rc.32026-11-17L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/MadDoooog/dsh-weixinbot#v0.1.0
ID: dsh-weixinbot@v0.1.0@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-17 · expires: 2026-11-24
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.2-rc.12026-11-05L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/MadDoooog/dsh-weixinbot#v0.1.0
ID: dsh-weixinbot@v0.1.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/MadDoooog/dsh-weixinbot#v0.1.0
ID: dsh-weixinbot@v0.1.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/MadDoooog/dsh-weixinbot#v0.1.0
ID: dsh-weixinbot@v0.1.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/MadDoooog/dsh-weixinbot#v0.1.0
ID: dsh-weixinbot@v0.1.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/MadDoooog/dsh-weixinbot#v0.1.0
ID: dsh-weixinbot@v0.1.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/MadDoooog/dsh-weixinbot#v0.1.0
ID: dsh-weixinbot@v0.1.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/MadDoooog/dsh-weixinbot#v0.1.0
ID: dsh-weixinbot@v0.1.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/MadDoooog/dsh-weixinbot#v0.1.0
ID: dsh-weixinbot@v0.1.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/MadDoooog/dsh-weixinbot#v0.1.0
ID: dsh-weixinbot@v0.1.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/MadDoooog/dsh-weixinbot#v0.1.0
ID: dsh-weixinbot@v0.1.0@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
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-16L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/MadDoooog/dsh-weixinbot#v0.1.0
ID: dsh-weixinbot@v0.1.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-23
View checks & evidence
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-11L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/MadDoooog/dsh-weixinbot#v0.1.0
ID: dsh-weixinbot@v0.1.0@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.3-alpha.22026-09-08L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/MadDoooog/dsh-weixinbot#v0.1.0
ID: dsh-weixinbot@v0.1.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.3-alpha.12026-09-07L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/MadDoooog/dsh-weixinbot#v0.1.0
ID: dsh-weixinbot@v0.1.0@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-10-04L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/MadDoooog/dsh-weixinbot#v0.1.0
ID: dsh-weixinbot@v0.1.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
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/dsh-weixinbot/?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.0dsh manifestv0.1.0git2026-11-19v0.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningfsWrite · files
src/adapter/cdn.ts:148fs.writeFileSync(full, buf) - warningfsWrite · files
src/credentials.ts:34fs.writeFileSync(file, JSON.stringify(creds, null, 2) + '\n', 'utf8') - warningfsWrite · files
src/credentials.ts:35fs.chmodSync(file, 0o600) - warningfsWrite · files
src/credentials.ts:50fs.writeFileSync(path.join(dir, 'cursor.json'), buf, 'utf8') - warningnetIp · network
src/server/health.ts:31this.log.info('[health] http://127.0.0.1:%d/health', this.cfg.port) - warningfsWrite · files
src/util.ts:96fs.appendFileSync(logFilePath, line)
show 5 audit findings
- mediumApproval decisions accepted from any whitelisted user, fromUserId is never checked against the owner
src/approval/bridge.ts:102The approval card is pushed to cfg.defaultTarget (the bound owner), but the /approve|/reject handler never compares fromUserId to defaultTarget. Any user present in allowUsers (the config supports multiple) can approve a privileged tool request the agent raised for the owner, bypassing the intended owner-only approval gate. The bridge also claims all approval/request events process-wide when enabled.
- mediumwechat_send tool sends to an arbitrary caller-supplied recipient, enabling exfiltration
src/notifier/tools.ts:63The tool is registered into the DSH toolbox and exposes an optional `to` that is passed verbatim to adapter.send with no allow-list. If the agent is steered by untrusted inbound WeChat content (prompt injection), it can be made to send conversation/secrets to an attacker-controlled WeChat id. This is a concrete, undocumented-at-config exfiltration channel.
- mediumMedia download trusts message-supplied full_url with no host allow-list, timeout, or pre-buffer size cap
src/adapter/cdn.ts:66The fetch target is taken directly from inbound item.media.full_url, so a malicious/compromised gateway or crafted media item can make the host issue requests to arbitrary (including internal) URLs (SSRF). fetchBytes has no timeout and buffers the whole response before the maxBytes check in saveMedia, so an oversized response can exhaust plugin/host memory or hang a turn.
- lowPlugin installs a process-wide uncaughtException handler that suppresses the host's default fatal exit
src/index.ts:47Adding an 'uncaughtException' listener disables Node's default terminate-on-uncaught-exception for the entire DSH host, not just this plugin. Any uncaught error anywhere in the host is swallowed and the process continues in a potentially corrupted state, which can mask real faults; the handler also appends to a log file. The listener is removed only on dispose.
- lowCredentials file is written before chmod 0600, leaving a brief world-readable window
src/credentials.ts:34On first creation the bot token is written with default umask permissions (commonly 0644) and only then chmod'ed to 0600; another local user can read the token during that window. The directory is also created without explicit restrictive mode.
WeChat bridge with defensible defaults (loopback health, 0600 creds, fail-closed whitelist), but approval decisions aren't bound to the owner and wechat_send allows arbitrary recipients.
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-08-15 · activity: Inactive
• Repo created: 2026-08-14
• Stars: ★ 0 · Forks: 0
• Health: Inactive — no commit in 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).
Frequently asked questions
What is dsh-weixinbot?
dsh-weixinbot 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 dsh-weixinbot?
Run dsh plugin --profile web add github:MadDoooog/dsh-weixinbot#v0.1.0 in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4); the web smoke test (L5) has not passed yet.
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-19 (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.
