Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
A dsh plugin that monitors files, command output, or WebSocket in the background, wakes the session on output, and offers a real-time viewing panel.
- Background monitoring for file, command, or WebSocket sources
- Wake on any output, or only lines matching a JS regex pattern
- WebSocket text/binary frame handling with close-code status
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 @caizhiyuan/dsh-tool-monitorInstall 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
Based on 1 requirement(s) across 2 @deepseek-ai/dsh-* packages. raw ranges
* ×2
✓ Running dsh 0.2.1-rc.2 is within the declared range — install is not blocked by version.
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.2.1-alpha.2 | dsh 0.2.0-rc.2 | dsh 0.2.0-rc.1 |
|---|---|---|---|---|---|
| 0.6.0 | · | · | · | · | · |
| 0.5.1 | ✓ | ◐ | ✓ | ✓ | · |
| v0.5.1 | · | · | · | · | · |
| 0.3.0 | · | · | · | · | ○ |
| 0.2.1 | · | · | · | · | · |
0.6.0npm2026-10-22
@caizhiyuan/dsh-tool-monitor
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.5.1npm✓ 3 runtime-verified◐ 1 testing2026-10-18
@caizhiyuan/dsh-tool-monitor
✓dsh 0.2.1-rc.2current2026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · @caizhiyuan/dsh-tool-monitor@0.5.1
ID: dsh-tool-monitor-2@0.5.1@dsh0.2.1-rc.2 · profile: l3-fullscan
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.
◐dsh 0.2.1-alpha.42026-10-18L4 · testing (install passed, runtime untested)
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · @caizhiyuan/dsh-tool-monitor@0.5.1
ID: dsh-tool-monitor-2@0.5.1@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
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.
✓dsh 0.2.1-alpha.22026-10-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · @caizhiyuan/dsh-tool-monitor@0.5.1
ID: dsh-tool-monitor-2@0.5.1@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
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.
✓dsh 0.2.0-rc.22026-10-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · @caizhiyuan/dsh-tool-monitor@0.5.1
ID: dsh-tool-monitor-2@0.5.1@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
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.
v0.5.1github2026-10-08
https://github.com/substitute525/dsh-tool-monitor
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.3.0npm2026-10-04
@caizhiyuan/dsh-tool-monitor
○dsh 0.2.0-rc.12026-09-30not tested
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · @caizhiyuan/dsh-tool-monitor@0.3.0
ID: dsh-tool-monitor-2@0.3.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
not present in web-profile loader inventory
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-25not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · @caizhiyuan/dsh-tool-monitor@0.3.0
ID: dsh-tool-monitor-2@0.3.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.7-rc.12026-09-24not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · @caizhiyuan/dsh-tool-monitor@0.3.0
ID: dsh-tool-monitor-2@0.3.0@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
View checks & evidence
not present in web-profile loader inventory
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-20not tested
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · @caizhiyuan/dsh-tool-monitor@0.3.0
ID: dsh-tool-monitor-2@0.3.0@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-10-04not tested
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · @caizhiyuan/dsh-tool-monitor@0.3.0
ID: dsh-tool-monitor-2@0.3.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.2.1npm2026-09-16
@caizhiyuan/dsh-tool-monitor
○dsh 0.1.6-alpha.12026-09-16not tested
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · @caizhiyuan/dsh-tool-monitor@0.2.1
ID: dsh-tool-monitor-2@0.2.1@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-23
View checks & evidence
not present in web-profile loader inventory
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-12not tested
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: npm · @caizhiyuan/dsh-tool-monitor@0.2.1
ID: dsh-tool-monitor-2@0.2.1@dsh0.1.5-rc.2 · profile: l3-fullscan
Issued: 2026-09-12 · expires: 2026-09-19
View checks & evidence
not present in web-profile loader inventory
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-tool-monitor-2/)``[](https://www.dsh.so/artifact/dsh-tool-monitor-2/)``[](https://www.dsh.so/artifact/dsh-tool-monitor-2/)`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 high (authoritative when present) → overall high.
v0.6.0dsh manifest0.6.0npm2026-10-250.6.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (3)
- criticalspawnShell · shell
lib/index.js:532: spawn(command, { ...options, shell: true })); - warningchildProcess · code-exec
lib/index.js:514spawn('taskkill', ['/PID', String(child.pid), '/T', '/F'], { windowsHide: true, stdio: 'ignore' }); - warningchildProcess · code-exec
lib/index.js:531? spawn('powershell.exe', ['-NoProfile', '-NonInteractive', '-Command', command], options)
show 4 audit findings
- highCommand monitors fall back to a direct local shell spawn, bypassing ctx.shell policy
lib/index.js:532When ctx.shell.start is not a function or ctx.shell.resolve throws, the model-supplied command string (monitor_start source=command) is executed by /bin/sh -c (or powershell.exe -Command on Windows) with the host process's full privileges. This deliberately bypasses the harness shell service's approval/allowlist/sandbox path, so a prompt-injected or malicious command can run without the host shell policy ever being consulted.
- mediumWS live-push endpoint authorizes only on a spoofable Host header and a sessionId query value
lib/index.js:706WebSocket handshakes are not subject to CORS and the browser always sets Host to the target (127.0.0.1:port), so the loopback check passes for any page in the user's browser. With a known or guessable sessionId, a cross-site page can open /tool-monitor/ws, receive monitor snapshots and read retained file/command output (mon.buffer) and stop monitors; no Origin, token, or authenticated-connection check is performed in this handler (unlike the HTTP route which uses connection.requestRejection).
- lowModel-supplied regular expression tested against unbounded file/WS output (ReDoS)
lib/index.js:853The pattern is compiled with no length or complexity bound and then run via mon.patternRe.test(delta) on file content or WS frames (up to 1 MiB of buffered command output). A catastrophic-backtracking pattern such as (a+)+$ over a large file blocks the single-threaded host event loop on every poll tick, stalling the harness.
- lowOutbound ws monitor accepts any destination, including internal/loopback hosts
lib/index.js:571monitor_start source=ws connects to a model-supplied URL with no destination policy, so the model (steered by untrusted content) can probe loopback or internal WebSocket services and have the responses surfaced into the session as notices — an SSRF-style reachability path that is inconsistent with the inbound loopback-only fence.
Command monitors can spawn arbitrary local shells outside ctx.shell policy, and the live WS endpoint authorizes only on a spoofable Host header with a session-id query parameter.
Rule (2026-10-24): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); without one, the static/vet fused tier applies. 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 static/vet.
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-08 · activity: Active
• Repo created: 2026-08-28
• Stars: ★ 0 · 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).