@aitcmhk-web/DSH-bot

通过 TG/微信实现离家办公：发布任务、语音聊天、切换模型、升级重启、自动记忆...Telegram / WeChat bridge plugin for DeepSeek Harness (DSH): bind your bot to a DSH workspace in one command, with handoff continuity between sessions.

PluginAutomationKnowledgeMediaNotificationsMemoryWeb search

Verification

L5 · Run tested

Verified

Risk

Medium

Health

Active

Trust

Silver

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

What it doesAI

Telegram/WeChat bridge bot that lets you remotely control a DSH workspace: publish tasks, voice chat, switch models, restart and auto-remember.

Bind a bot to a DSH workspace with a single command
Publish tasks and chat by voice from Telegram or WeChat
Switch models, restart/upgrade and keep session memory continuity

automationAInotificationAImemoryAI

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-botplugin

verified 1.0.8

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 ＼ dsh	dsh 0.2.1-rc.2 current	dsh 0.2.1-alpha.4	dsh 0.2.1-alpha.2
1.0.8	✓	✓	✓

Install compatibility (by plugin version, dsh versions within)

Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed

1.0.8npm✓ 3 runtime-verified2026-10-19

dsh-botplugin

✓dsh 0.2.1-rc.2current2026-10-19L5 · runtime verified

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-rc.2
• Plugin artifact: npm · dsh-botplugin@1.0.8

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-bot-2@1.0.8@dsh0.2.1-rc.2 · profile: l4-sandbox

Issued: 2026-10-19 · expires: 2026-10-26

View checks & evidence

L1 · Found✓ Passed

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L2 · Structured✓ Passed

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L3 · Install spec✓ Passed

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

Source: registry verification · Method: install spec parse · Captured 2026-10-18

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

Source: registry verification · Method: DSH version declaration · Captured 2026-10-18

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19

spec dsh-botplugin · channel npm package · outcome ran · exit 0

check took: 2.8s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19

spec dsh-botplugin · channel npm package · outcome ran · exit 0

check took: 2.8s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19

spec dsh-botplugin · channel npm package · outcome ran · exit 0

check took: 2.8s

L5 · Run tested✓ Passed

active in loader tree (150 entries)

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19

spec dsh-botplugin · install mode reused L4 scratch

check took: 62ms

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

Source: DSH runtime · Method: web boot · Captured 2026-10-19

ready line dsh web: http://127.0.0.1:65356/?token=…

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

Source: DSH runtime · Method: HTTP request · Captured 2026-10-19

path / · HTTP 200 · took 62ms

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE✓ Passed

Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-19

verdict active · entries 150

match: include:botplugin · dsh-botplugin · 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.42026-10-17L5 · runtime verified

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-alpha.4
• Plugin artifact: npm · dsh-botplugin@1.0.8

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-alpha.4

ID: dsh-bot-2@1.0.8@dsh0.2.1-alpha.4 · profile: l4-sandbox

Issued: 2026-10-17 · expires: 2026-10-24

View checks & evidence

L1 · Found✓ Passed

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L2 · Structured✓ Passed

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L3 · Install spec✓ Passed

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

Source: registry verification · Method: install spec parse · Captured 2026-10-18

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

Source: registry verification · Method: DSH version declaration · Captured 2026-10-18

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-17

spec dsh-botplugin · channel npm package · outcome ran · exit 0

check took: 4.2s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-17

spec dsh-botplugin · channel npm package · outcome ran · exit 0

check took: 4.2s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-17

spec dsh-botplugin · channel npm package · outcome ran · exit 0

check took: 4.2s

L5 · Run tested✓ Passed

active in loader tree (150 entries)

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-17

spec dsh-botplugin · install mode reused L4 scratch

check took: 343ms

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

Source: DSH runtime · Method: web boot · Captured 2026-10-17

ready line dsh web: http://127.0.0.1:63359/?token=…

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

Source: DSH runtime · Method: HTTP request · Captured 2026-10-17

path / · HTTP 200 · took 343ms

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE✓ Passed

Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-17

verdict active · entries 150

match: include:botplugin · dsh-botplugin · 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 · runtime verified

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-alpha.2
• Plugin artifact: npm · dsh-botplugin@1.0.8

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-alpha.2

ID: dsh-bot-2@1.0.8@dsh0.2.1-alpha.2 · profile: l3-fullscan

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

View checks & evidence

L1 · Found✓ Passed

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L2 · Structured✓ Passed

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L3 · Install spec✓ Passed

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

Source: registry verification · Method: install spec parse · Captured 2026-10-18

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

Source: registry verification · Method: DSH version declaration · Captured 2026-10-18

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14

spec dsh-botplugin · channel npm package · outcome ran · exit 0

check took: 3.1s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14

spec dsh-botplugin · channel npm package · outcome ran · exit 0

check took: 3.1s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14

spec dsh-botplugin · channel npm package · outcome ran · exit 0

check took: 3.1s

L5 · Run tested✓ Passed

active in loader tree (150 entries)

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14

spec dsh-botplugin · install mode reused L4 scratch

check took: 176ms

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

Source: DSH runtime · Method: web boot · Captured 2026-10-14

ready line dsh web: http://127.0.0.1:59559/?token=…

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

Source: DSH runtime · Method: HTTP request · Captured 2026-10-14

path / · HTTP 200 · took 176ms

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE✓ Passed

Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-14

verdict active · entries 150

match: include:botplugin · dsh-botplugin · 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.

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:

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-bot-2Automated review · daily

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

static medium→dynamic medium→overall medium

0 critical·3 high

mediumoverall · medium

1static scan · vet primaryvet AST static analysis (npm artifact or git source)

Version binding

plugin versionv1.0.8dsh manifest

scanned version1.0.8npm2026-10-21

current version1.0.8same version

vet verdictsuspicious · npm

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

show static findings (8)

warningchildProcess · code-execqr-terminal.mjs:335
const res = spawnSync('osascript', args, { encoding: 'utf8', timeout: 15000 });
warningchildProcess · code-execqr-terminal.mjs:350
const qrRes = spawnSync('qrencode', ['-l', 'M', '-s', '1', '-m', '2', '-o', '-', text], {
warningcurlDownload · networksetup-bot.sh:20
if curl -fsSL --max-time 60 "$URL" -o "$TMP" 2>/dev/null && [ -s "$TMP" ]; then
warningcurlDownload · networksetupdsh-helper.sh:24
if curl -fsSL --max-time 25 "$SETUPDSH_URL" -o "${SELF_PATH}.new" 2>/dev/null \
warningchildProcess · code-execsrc/asr.js:251
const child = spawn(
warningshellExec · shellsrc/asr.js:80
const out = execFileSync('which', [name], { timeout: 3000 });
warningshellExec · shellsrc/asr.js:139
execFileSync(bin, ['-c', 'import funasr'], { timeout: 60_000, stdio: 'ignore' });
warningshellExec · shellsrc/asr.js:196
const out = execFileSync('/usr/bin/vm_stat', [], { timeout: 5000 }).toString();

2dynamic auditmodel reads redacted source context · never executes plugin code

highest grademedium

merged intooverall medium

audited at2026-10-17

findings0 critical·0 high1 medium / 3 low hidden

show 4 audit findings

mediumRuntime helper downloads setupdsh.sh from a mutable branch and executes it, with only a static marker as checksetupdsh-helper.sh:29
The file header states this helper is invoked by the bot's /setupdsh menu command, so a chat command causes the latest setupdsh.sh from https://raw.githubusercontent.com/aitcmhk-web/DSH-bot/main/setupdsh.sh to be downloaded and run with the host user's privileges. The 'setupdsh-self-marker' grep is a sanity check, not integrity verification: there is no pinning, hash or signature, so a compromise/typo of the repo, a force-push to main, or a SETUPDSH_URL override turns this into arbitrary shell execution on the machine running the bot.
lowLegacy entry script downloads a second remote script and runs it via /bin/sh without verificationsetup-bot.sh:21
Running this script executes whatever currently sits at setupbot.sh on the main branch, with no pinning or checksum, and the URL is overridable through SETUPBOT_URL. The user trusts the wrapper but the wrapper forwards execution to unpinned remote content (same trust class as the helper above, but requires the user to start the script).
lowPredictable /tmp fallback path is written by curl and then executed as a shell scriptsetup-bot.sh:18
When mktemp fails, the download target becomes a predictable, PID-based name in the world-writable /tmp. curl -o follows a pre-existing symlink, so a local user who can pre-create /tmp/setupbot.<pid>.sh can influence the bytes that are then run by /bin/sh (and, in the symlink case, cause the write to land on another file the victim can write). Requires local access, hence low.
lowTelegram bot token is passed as a curl URL argument, exposing it in the process listrestart-helper.sh:108
The token reaches curl as part of argv, so it appears in `ps`/`/proc/<pid>/cmdline` for the lifetime of the request and is visible to other local users on the host. The token itself is not written to the restart log (checked), so the leak is limited to the process listing, but this is the bot's full control credential.

JS modules reviewed are defensively written; residual risk sits in shipped shell helpers that fetch and execute unpinned remote scripts and expose a Telegram token in argv.

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

• Repo created: 2026-09-28

• Stars: ★ 1 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/aitcmhk-web/DSH-bot

Plugin notes

What is the @aitcmhk-web/DSH-bot DeepSeek Harness plugin?

@aitcmhk-web/DSH-bot is a DeepSeek Harness plugin maintained by @aitcmhk-web. It is cataloged on dsh.so as a Automation plugin for Notifications tasks, with a public GitHub source, declared install command, and automated static scan results; plugins static-flagged at warn or above also carry a model-driven dynamic security audit record.

How do I install @aitcmhk-web/DSH-bot?

Run dsh plugin --profile web add dsh-botplugin in a DeepSeek Harness (dsh) environment. This exact command has been verified by a real install inside an isolated windows-acl sandbox (L4) plus web smoke testing (L5).

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 (it can produce false positives and miss context), and the dynamic security audit has a model read the harvested source context with secret files stripped and content redacted inline — plugin code is never executed. The dynamic audit only covers plugins static-flagged at warn or above, and its conclusion can only raise the combined verdict, never exempt it. Neither layer is a manual security audit or an endorsement; before using a plugin, review the repository and installed permissions, and combine both with the verification level (L4/L5) and health signals.

"DeepSeek Harness (dsh) is an open-source agent harness developed by DeepSeek AI. It uses an architecture where everything is a plugin, and is powered by Cordis."
— DeepSeek Harness README

Sources: GitHub repository · DeepSeek Harness README · security scan data · Maintained by dsh.so · Last updated 2026-10-19

@aitcmhk-web/DSH-bot

What it doesAI

Installation

Verification & Compatibility

Author badges

Security Report

Activity

Source

Author README