Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
Runtime observability and diagnostics panel for DSH, showing plugin tree, loader status, session activity, and compatibility with plugin management.
- Combines profile config, installed packages, loader status, and session activity into one report.
- Plugin tree supports disable, activate, uninstall, and update actions.
- Standalone diagnostic page auto-opens on plugin-caused startup failures and works without DSH web UI.
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-insight-treeInstall 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 2 requirement(s) across 3 @deepseek-ai/dsh-* packages. raw ranges
^0.1.2-rc.1 ×2 >=0.1.2-rc.1 <0.2.0-0 ×1
✗ Running dsh 0.2.1-rc.2 is outside the declared range — the official install gate rejects it (incompatible-version).
To force-install, grant an exact-version exemption: dsh plugin allow-version dsh-insight-tree@0.1.2 0.2.1-rc.2 (the exemption lives in the local profile; this site does not assume one)
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.2 | dsh 0.2.0-rc.2 | dsh 0.1.7-rc.2 | dsh 0.1.7-rc.1 |
|---|---|---|---|---|---|
| 0.1.2 | ✓ | ✓ | ✓ | ✓ | ✓ |
| 0.1.1 | · | · | · | · | · |
0.1.2npm✓ 9 runtime-verified2026-10-20
dsh-insight-tree
✓dsh 0.2.1-rc.2current2026-10-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-insight-tree@0.1.2
ID: dsh-insight-tree@0.1.2@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
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.22026-10-12L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-insight-tree@0.1.2
ID: dsh-insight-tree@0.1.2@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
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 · dsh-insight-tree@0.1.2
ID: dsh-insight-tree@0.1.2@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.
✓dsh 0.1.7-rc.22026-09-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-insight-tree@0.1.2
ID: dsh-insight-tree@0.1.2@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
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.1.7-rc.12026-09-24L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · dsh-insight-tree@0.1.2
ID: dsh-insight-tree@0.1.2@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
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.1.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · dsh-insight-tree@0.1.2
ID: dsh-insight-tree@0.1.2@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
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.1.6-alpha.12026-09-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · dsh-insight-tree@0.1.2
ID: dsh-insight-tree@0.1.2@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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.1.5-rc.22026-09-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: npm · dsh-insight-tree@0.1.2
ID: dsh-insight-tree@0.1.2@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-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.
✓prehistory2026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-insight-tree@0.1.2
ID: dsh-insight-tree@0.1.2@dshunknown · profile: l3-fullscan
Issued: 2026-09-30 · expires: 2026-10-07
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.
0.1.1npm✓ 1 runtime-verified2026-09-08
dsh-insight-tree
✓dsh 0.1.3-alpha.22026-09-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: npm · dsh-insight-tree@0.1.1
ID: dsh-insight-tree@0.1.1@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
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-insight-tree/)``[](https://www.dsh.so/artifact/dsh-insight-tree/)``[](https://www.dsh.so/artifact/dsh-insight-tree/)``[](https://www.dsh.so/artifact/dsh-insight-tree/)``[](https://www.dsh.so/artifact/dsh-insight-tree/)``[](https://www.dsh.so/artifact/dsh-insight-tree/)`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 medium — stricter wins → overall medium.
v0.1.2dsh manifest0.1.2npm2026-10-220.1.2same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (12)
- warningchildProcess · code-exec
bin/diagnose.mjs:33return spawnSync(command.file, [...command.args, ...args], { encoding: 'utf8', windowsHide: true, shell: process.platform === 'win32', timeo - warningnetIp · network
bin/diagnose.mjs:236console.log(`DSH Insight Tree 诊断页面：http://127.0.0.1:${port}/?${query.toString()}`) - warningfsWrite · files
bin/diagnose.mjs:66fs.writeFileSync(overlay, yaml.dump([{ id, disabled }], { noRefs: true, lineWidth: -1 }), 'utf8') - warningfsWrite · files
bin/diagnose.mjs:77fs.writeFileSync(profileFile, yaml.dump(next, { noRefs: true, lineWidth: -1 }), 'utf8') - warningfsWrite · files
bin/diagnose.mjs:91if (cleaned.removed > 0) fs.writeFileSync(file, yaml.dump(cleaned.entries, { noRefs: true, lineWidth: -1 }), 'utf8') - warningchildProcess · code-exec
bin/web-with-diagnostics.mjs:29const diagnostic = spawn(process.execPath, [script, '--profile', profile, '--port', String(port)], { detached: true, stdio: 'ignore', window - warningchildProcess · code-exec
bin/web-with-diagnostics.mjs:38const opener = spawn(process.env.ComSpec ?? 'cmd.exe', ['/d', '/c', 'start', '', url], { detached: true, stdio: 'ignore', windowsHide: true - warningchildProcess · code-exec
bin/web-with-diagnostics.mjs:42const opener = spawn('open', [url], { detached: true, stdio: 'ignore' }) - warningnetIp · network
bin/web-with-diagnostics.mjs:28const url = `http://127.0.0.1:${port}/?profile=${encodeURIComponent(profile)}` - warningnetIp · network
bin/web-with-diagnostics.mjs:69const request = http.get(`http://127.0.0.1:${port}/`, (response) => { response.resume(); if (response.statusCode && response.statusCode < 50 - warningchildProcess · code-exec
lib/index.js:1244if (!invocation.viaShell || process.platform !== "win32") return spawn(invocation.file, [...invocation.args, ...args], { - warningchildProcess · code-exec
lib/index.js:1254return spawn(process.env.ComSpec ?? "cmd.exe", [
show 5 audit findings
- mediumStandalone diagnose server has no token and no Host check, exposing plugin uninstall/disable endpoints
bin/diagnose.mjs:19web-with-diagnostics.mjs spawns this server as `spawn(process.execPath, [script, '--profile', profile, '--port', String(port)], ...)` without --token, so authOk() always returns true. The server listens on 127.0.0.1 but never validates the Host header and its POST /uninstall, /disable, /enable handlers run `dsh plugin remove` and rewrite cordis.patch.yml. Any local process, or a remote page using DNS rebinding to a random/known port, can trigger plugin removal or shutdown of the user's tooling; removal also re-runs package installation with the release-age policy disabled.
- mediumEmbedded route has an empty default token, so plugin disable/uninstall/update can be triggered by cross-site POST
lib/index.jsConfig schema `token: z.string().default("")` means the check is skipped by default. A page the user visits can POST (simple request, no preflight, response unread) to http://127.0.0.1:<port>/dsh-insight-tree/uninstall?id=<plugin>, /disable, or /update?version=...&confirm=1, causing plugin removal, disabling, or downgrade to an older published version without any user interaction. The only barrier is the loopback Host header, which does not stop browser-originated requests to 127.0.0.1.
- lowBootstrap endpoint returns the access token without authentication
lib/index.jsThe token check explicitly exempts `/dsh-insight-tree/bootstrap` and that endpoint echoes the token to any caller that supplies a loopback Host header. Combined with the empty-token default this removes the last barrier: a request that can reach the server (local process, or any path where the Host header can be forged) can obtain the token and then call every mutating endpoint as an authenticated client.
- lowDeliberately retries dsh/pnpm operations with minimum-release-age disabled
lib/index.jsWhen a remove/add fails with a MINIMUM_RELEASE_AGE / supply-chain policy error, the code silently retries with `--config.minimum-release-age=0` (also in applyPluginUpdate's runAdd and in bin/diagnose.mjs). Because these commands re-resolve and install dependencies, the cooldown that protects against freshly published (possibly compromised) versions is bypassed; the user is only told afterwards in the result message.
- lowPlugin monkey-patches the shared host tools.register service
lib/index.jsapply() replaces `ctx.get('tools').register` on the host with a wrapper that stores the calling fiber name and then delegates. This is a global mutation of a shared service used by every other plugin; the wrapper swallows all errors from the introspection block and its global `toolsPatched` flag is shared across contexts, which can suppress attribution or, if the host API changes, interfere with tool registration. It is done without any host-provided extension point.
No critical/high issues; the plugin's local HTTP endpoints let an unauthenticated caller disable, uninstall or update plugins (default empty token), and it bypasses pnpm's release-age policy.
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-09-10 · activity: Stable
• Repo created: 2026-09-07
• Stars: ★ 0 · Forks: 0
• Health: Stable — committed within 90 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).