Humanized fork of @xmanrui/dsh-im (base 4.21.2): humanized message delivery with send-delay + typing two-phase, message_break + streaming coexistence, status reactions, reply quotes, per-bot overrides and a no_reply reclaim tool for DeepSeek Harness IM channels.
Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
Humanized IM message delivery for DeepSeek Harness bots: send delays, typing indicators, status reactions, reply quotes and per-bot overrides.
- Two-phase send-delay plus typing indicator delivery
- message_break coexists with streaming replies
- Status reactions, reply quotes, per-bot overrides and no_reply reclaim tool
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:john-walks-slow/dsh-im-humanize#v4.38.0-humanize.1security scan passed · source release v4.38.0-humanize.1
Install 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.
| plugin \ dsh | dsh 0.2.1-rc.2 current | dsh 0.2.1-alpha.2 |
|---|---|---|
| v4.38.0-humanize.1 | ✓ | · |
| v4.21.2-humanize.3 | · | ✓ |
v4.38.0-humanize.1github✓ 1 runtime-verified2026-10-18
https://github.com/john-walks-slow/dsh-im-humanize
✓dsh 0.2.1-rc.2current2026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/john-walks-slow/dsh-im-humanize#v4.38.0-humanize.1
ID: dsh-im-humanize@v4.38.0-humanize.1@dsh0.2.1-rc.2 · 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.
v4.21.2-humanize.3github✓ 1 runtime-verified2026-10-15
https://github.com/john-walks-slow/dsh-im-humanize
✓dsh 0.2.1-alpha.22026-10-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/john-walks-slow/dsh-im-humanize#v4.21.2-humanize.3
ID: dsh-im-humanize@v4.21.2-humanize.3@dsh0.2.1-alpha.2 · profile: l3-fullscan
Issued: 2026-10-15 · expires: 2026-10-22
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-im-humanize/)``[](https://www.dsh.so/artifact/dsh-im-humanize/)`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.
v4.38.0-humanize.1dsh manifestv4.38.0-humanize.1git2026-10-21v4.38.0-humanize.1same 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-15 · activity: Active
• Repo created: 2026-09-07
• Stars: ★ 4 · Forks: 0
• Health: Active — committed within last 30 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).
