@zhuweiyou/dsh-plugin-clawbot avatar

@zhuweiyou/dsh-plugin-clawbot

DSH(DeepSeek Harness)的微信 ClawBot 通道插件

PluginNetworkNotifications
Verification
L5 · Run tested
Verified
Risk
LowRisk
Health
Active
Trust
Gold

Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →

Install verification badge dsh 0.2.1-rc.2

What it doesAI

DSH channel plugin bridging WeChat ClawBot messages to DSH sessions, with QR-code login, /model switching and a settings panel.

  • Bidirectional WeChat <-> DSH messaging: text, images, transcribed voice
  • QR-code bind/rebind; shares ClawBot credentials with OpenClaw safely
  • /model command to view and switch session model; panel in DSH Web settings
networkAInotificationAI

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 dsh-plugin-clawbot
verified 0.6.0

Install method: npm · 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

Declared DSH compatibilityfrom package.json · peerDependencies
author declared no dsh version requirement

○ The author declares no dsh version requirement — install is not blocked by version.

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)
At-a-glance → evidence in the cards below
plugin \ dshdsh 0.2.1-rc.2
current
dsh 0.2.1-alpha.2
0.6.0✓✗
v0.6.0··
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
0.6.0npm✓ 1 runtime-verified1 failed2026-10-20

dsh-plugin-clawbot

✓dsh 0.2.1-rc.2current2026-10-20L5 · runtime verified
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-rc.2
  • • Plugin artifact: npm · dsh-plugin-clawbot@0.6.0
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Passed
L5 runtime
Passed
Install + runtime smoke verified in the dsh sandbox — installs and runs
L5 · runtime verified · valid for dsh 0.2.1-rc.2

ID: dsh-plugin-clawbot@0.6.0@dsh0.2.1-rc.2 · profile: l4-sandbox

Issued: 2026-10-20 · expires: 2026-10-27

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-18
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-18
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-20
spec dsh-plugin-clawbot · channel npm package · outcome ran · exit 0
check took: 2.1s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-20
spec dsh-plugin-clawbot · channel npm package · outcome ran · exit 0
check took: 2.1s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-20
spec dsh-plugin-clawbot · channel npm package · outcome ran · exit 0
check took: 2.1s
L5 · Run tested✓ Passed

active in loader tree (150 entries)

Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-20
spec dsh-plugin-clawbot · install mode reused L4 scratch
check took: 383ms
Web boot ready✓ Passed
Source: DSH runtime · Method: web boot · Captured 2026-10-20
ready line dsh web: http://127.0.0.1:49177/?token=…
HTTP endpoint served✓ Passed
Source: DSH runtime · Method: HTTP request · Captured 2026-10-20
path / · HTTP 200 · took 383ms
Plugin active in inventory✓ Passed
Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-20
verdict active · entries 150
match: include:clawbot · dsh-plugin-clawbot · phase active
phases: active 122 · null 28

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-15L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-alpha.2
  • • Plugin artifact: npm · dsh-plugin-clawbot@0.6.0
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Passed
L5 runtime
Failed
Sandbox install failed
L5 · failed

ID: dsh-plugin-clawbot@0.6.0@dsh0.2.1-alpha.2 · profile: l3-fullscan

Issued: 2026-10-15 · expires: 2026-10-22

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-18
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-18
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14
spec dsh-plugin-clawbot · channel npm package · outcome ran · exit 0
check took: 5.9s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14
spec dsh-plugin-clawbot · channel npm package · outcome ran · exit 0
check took: 5.9s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14
spec dsh-plugin-clawbot · channel npm package · outcome ran · exit 0
check took: 5.9s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14
spec dsh-plugin-clawbot · install mode reused L4 scratch
check took: 0ms
Web boot ready✕ Failed
boot failed
HTTP endpoint served✕ Failed

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

v0.6.0github2026-10-14

https://github.com/zhuweiyou/dsh-plugin-clawbot

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

Author badges

Embed the official badges in your README to showcase security & install-test status:

dsh.so risk
`[![dsh.so risk](https://www.dsh.so/badge/dsh-plugin-clawbot.svg)](https://www.dsh.so/artifact/dsh-plugin-clawbot/)`
dsh 0.2.1-rc.2 install verified
`[![dsh.so install · dsh 0.2.1-rc.2](https://www.dsh.so/badge/install/dsh-plugin-clawbot@0.2.1-rc.2.svg)](https://www.dsh.so/artifact/dsh-plugin-clawbot/)`

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.

dsh-plugin-clawbotAutomated review · daily

Static low, dynamic medium — stricter wins → overall medium.

static low→dynamic medium→overall medium
0 critical·0 high
mediumoverall · medium
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
plugin versionv0.6.0dsh manifest
scanned version0.6.0npm2026-10-21
current version0.6.0same version
vet verdictclean · npm

Vet is an AST static scan (npm artifact or git source).

show static findings (6)
  • warningnetIp · networklib/config.js:119

    baseUrl: (_c = (_b = env.DSH_BASE_URL) != null ? _b : (_a2 = file.dsh) == null ? void 0 : _a2.baseUrl) != null ? _c : "http://127.0.0.1:3080

  • warningfsWrite · fileslib/config.js:53

    fs.writeFileSync(path.join(dir, "accounts.json"), JSON.stringify([...existing, accountId], null, 2), "utf-8");

  • warningfsWrite · fileslib/config.js:59

    fs.writeFileSync(path.join(weixinStateDir(), "accounts.json"), JSON.stringify(updated, null, 2), "utf-8");

  • warningfsWrite · fileslib/config.js:76

    fs.writeFileSync(filePath, JSON.stringify(data, null, 2), "utf-8");

  • warningnetIp · networklib/dsh.js:303

    const { httpBase, wsBase } = splitBases(baseUrl != null ? baseUrl : "http://127.0.0.1:3080");

  • warningfsWrite · fileslib/state.js:81

    fs.writeFileSync(tmp, JSON.stringify(value, null, 2), "utf-8");

2model reads redacted source context · never executes plugin code
highest grademedium
merged intooverall medium
audited at2026-10-19
findings0 critical·0 high2 medium / 1 low hidden
show 3 audit findings
  • mediumallowFrom defaults to empty, so every WeChat sender can drive a local DSH agent sessionlib/config.js:127

    With the shipped defaults the sender filter in lib/manager.js (`if (this.wxCfg.allowFrom.length > 0 && !this.wxCfg.allowFrom.includes(fromUserId))`) is skipped, so any WeChat user who can message the bound ClawBot is queued into processForPeer, gets a DSH session created in the configured cwd and can prompt the agent, which exposes whatever tools/filesystem access the agent has. There is no authentication of the sender beyond this list.

  • mediumState-changing /clawbot/api endpoints protected only by Host header, no Origin/CSRF validationlib/index.js:95

    isLoopbackHost only rejects DNS-rebinding style requests. A page on any website the user visits can issue a CORS-simple cross-site POST (e.g. content-type text/plain with body "{}") to /clawbot/api/unbind, /clawbot/api/login/start or /clawbot/api/login/cancel; readBody accepts JSON regardless of content-type, so the side effect runs. Concrete result: the stored WeChat credentials are deleted and the bridge is paused (lib/manager.js unbind -> clearAccount), or repeated login flows are triggered.

  • lowRemote-supplied accountId used unsanitised in filesystem pathslib/config.js:75

    saveAccount is called from lib/manager.js with accountId taken from the WeChat QR-confirm response (resp.ilink_bot_id), and clearAccount unlinks `${accountId}.json|.sync.json|.context-tokens.json`. A malicious or compromised ilink endpoint returning an id containing path separators could make the plugin write/delete files outside the accounts directory. Requires control of the upstream HTTPS endpoint, so impact is limited.

Strong guards (CDN allowlist, size caps, 0600 token files), but the loopback /clawbot/api routes lack Origin/CSRF checks and allowFrom defaults to accept every WeChat sender.

Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.

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-18 · activity: Active

• Repo created: 2026-09-01

• Stars: ★ 1 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/zhuweiyou/dsh-plugin-clawbot

Was this page helpful?