Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
DSH web-mode plugin showing current version in General Settings with buttons to check and apply updates.
- Displays current DSH version at bottom of General Settings
- Button to check for updates
- Button to update to latest version
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-version-pluginInstall 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
^0.1.0-rc.7 || ^0.1.1-rc.2 ×2
✗ 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-version-plugin@1.0.1 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.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 | dsh 0.2.0-rc.1 |
|---|---|---|---|---|---|
| 1.0.1 | ✓ | ✗ | ✓ | ✓ | ✓ |
1.0.1npm✓ 12 runtime-verified◐ 1 testing1 failed2026-10-19
dsh-version-plugin
✓dsh 0.2.1-rc.2current2026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-version-plugin@1.0.1
ID: dsh-version-plugin@1.0.1@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
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-16L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-version-plugin@1.0.1
ID: dsh-version-plugin@1.0.1@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
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 · dsh-version-plugin@1.0.1
ID: dsh-version-plugin@1.0.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-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-version-plugin@1.0.1
ID: dsh-version-plugin@1.0.1@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-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.
✓dsh 0.2.0-rc.12026-09-29L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-version-plugin@1.0.1
ID: dsh-version-plugin@1.0.1@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
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-version-plugin@1.0.1
ID: dsh-version-plugin@1.0.1@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-version-plugin@1.0.1
ID: dsh-version-plugin@1.0.1@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-version-plugin@1.0.1
ID: dsh-version-plugin@1.0.1@dsh0.1.6-alpha.2 · profile: l3-fullscan
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-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · dsh-version-plugin@1.0.1
ID: dsh-version-plugin@1.0.1@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-23
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-version-plugin@1.0.1
ID: dsh-version-plugin@1.0.1@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.
✓dsh 0.1.5-rc.12026-09-10L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.1
- • Plugin artifact: npm · dsh-version-plugin@1.0.1
ID: dsh-version-plugin@1.0.1@dsh0.1.5-rc.1 · profile: l4-sandbox
Issued: 2026-09-10 · expires: 2026-09-17
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.3-alpha.22026-09-09L4 · testing (install passed, runtime untested)
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: npm · dsh-version-plugin@1.0.1
ID: dsh-version-plugin@1.0.1@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-16
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.1.2-rc.12026-09-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: npm · dsh-version-plugin@1.0.1
ID: dsh-version-plugin@1.0.1@dsh0.1.2-rc.1 · profile: l5-web-smoke
Issued: 2026-09-09 · expires: 2026-12-08
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-10-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-version-plugin@1.0.1
ID: dsh-version-plugin@1.0.1@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
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-version-plugin/)``[](https://www.dsh.so/artifact/dsh-version-plugin/)``[](https://www.dsh.so/artifact/dsh-version-plugin/)``[](https://www.dsh.so/artifact/dsh-version-plugin/)``[](https://www.dsh.so/artifact/dsh-version-plugin/)``[](https://www.dsh.so/artifact/dsh-version-plugin/)``[](https://www.dsh.so/artifact/dsh-version-plugin/)``[](https://www.dsh.so/artifact/dsh-version-plugin/)``[](https://www.dsh.so/artifact/dsh-version-plugin/)`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 (authoritative when present) → overall medium.
v1.0.1dsh manifest1.0.1npm2026-10-241.0.1same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (3)
- criticalshellExec · shell
lib/index.js:55const globalRoot = execSync("npm root -g", { encoding: "utf-8", stdio: ["pipe", "pipe", "ignore"] }).trim(); - criticalshellExec · shell
lib/index.js:61const dshPath = execSync("which dsh", { encoding: "utf-8", stdio: ["pipe", "pipe", "ignore"] }).trim(); - warningchildProcess · code-exec
lib/index.js:96const child = spawn("npm", ["install", "-g", "@deepseek-ai/dsh@latest"], { shell: false });
show 2 audit findings
- mediumLoopback RPC endpoint updateToLatest performs an unconfirmed global 'npm install -g' on request
lib/index.js:96Any client that can reach the loopback DSH RPC channel can invoke /dsh-version updateToLatest and cause the host user to run a privileged global npm install of @latest. The server does not itself compare the installed version with the latest one (that check exists only in the browser UI), does not require an extra confirmation/token, and npm installs execute the package's own lifecycle scripts, so whatever the registry serves at that moment runs with the user's privileges. Arguments are constant, so this is not arbitrary command injection, but it is a state-changing, privileged, network-driven
- lowexecSync fallbacks resolve 'npm'/'which' through PATH in a shell
lib/index.js:55Both commands are constant strings with no interpolation, and each is wrapped in try/catch reached only when package.json resolution fails, so there is no attacker-controlled input path. Residual risk is only that a manipulated PATH could make a different 'npm'/'which' binary run as the host user; exploiting that already requires control over the DSH process environment.
Version/update plugin for DSH; constant-argument execSync/spawn are guarded, but the loopback RPC endpoint updateToLatest triggers a global npm install with no server-side confirmation.
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-09-01 · activity: Stable
• Repo created: 2026-08-28
• Stars: ★ 1 · 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).
