Multi-channel decision and remote-control bridge for DeepSeek Harness: pushes any workspace's approval/question cards to IM channels (WeChat iLink first) and answers them from chat, with a session console, per-channel security and an open push service. Maintenance status: FROZEN since 2026-10-05.
Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
Multi-channel decision & remote-control bridge for DeepSeek Harness: pushes approval cards to IM and answers from chat.
- Support WeChat iLink IM channels
- Answer authorization and question cards from chat
- Per-channel security and open push service
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-reach@0.1.22security scan passed · npm package v0.1.22
Install method: npm · sandbox install ok, web smoke failed (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
Based on 1 requirement(s) across 26 @deepseek-ai/dsh-* packages. raw ranges
>=0.1.2-rc.1 <0.2.0 || >=0.1.5-alpha.1 <0.2.0 || >=0.1.6-0 <0.2.0 || >=0.1.7-0 <0.2.0 || >=0.2.0-0 <0.3.0 || >=0.2.1-0 <0.3.0 ×26
✓ Running dsh 0.2.1-rc.2 is within the declared range — install is not blocked by version.
Footnote: the author also wrote engines.dsh = ">=0.1.2-rc.1 <0.2.0 || >=0.1.5-alpha.1 <0.2.0 || >=0.1.6-0 <0.2.0 || >=0.1.7-0 <0.2.0 || >=0.2.0-0 <0.3.0 || >=0.2.1-0 <0.3.0" — DSH does not read that field (not part of the verdict).
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| plugin ＼ dsh | dsh 0.2.1-rc.2 current | dsh 0.2.1-alpha.4 | dsh 0.1.7-rc.1 |
|---|---|---|---|
| 0.1.22 | ✗ | · | · |
| v0.1.22 | ◐ | · | · |
| 0.1.20 | · | ✗ | · |
| 0.1.18 | · | · | · |
| 0.1.17 | · | · | · |
0.1.22npm1 failed2026-10-21
dsh-reach
✗dsh 0.2.1-rc.2current2026-10-21L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-reach@0.1.22
ID: dsh-reach@0.1.22@dsh0.2.1-rc.2 · profile: l3-fullscan
Issued: 2026-10-21 · expires: 2026-10-28
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.1.22github◐ 1 testing2026-10-19
https://github.com/PerryLink/dsh-reach
◐dsh 0.2.1-rc.2current2026-10-19L4 · testing (install passed, runtime untested)
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/PerryLink/dsh-reach#v0.1.22
ID: dsh-reach@v0.1.22@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.1.20npm1 failed2026-10-18
dsh-reach
✗dsh 0.2.1-alpha.42026-10-18L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-reach@0.1.20
ID: dsh-reach@0.1.20@dsh0.2.1-alpha.4 · profile: l5-web-smoke
Issued: 2026-10-18 · expires: 2027-01-16
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.1.18npm2026-10-18
dsh-reach
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.1.17npm2026-10-10
dsh-reach
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
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-reach/)`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 no conclusion — stricter wins → overall low.
v0.1.22dsh manifest0.1.22npm2026-10-210.1.22same versionclean · npmVet is an AST static scan (npm artifact or git source).
not in the dynamic queue (queue only covers plugins static-flagged at warn or above) — this does not mean the dynamic audit found it safe.
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-20 · activity: Active
• Repo created: 2026-09-03
• Stars: ★ 2 · Forks: 0
• Health: Active — committed within last 30 days
Source
GitHub: github.com/PerryLink/dsh-reach
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).