dsh-sm-version-display avatar

dsh-sm-version-display

用于在侧边栏“设置”按钮上方显示已安装 dsh 版本的 DeepSeek Harness Web 插件。 | DeepSeek Harness Web plugin that displays the installed dsh version above the sidebar Settings button.

PluginUI & SkinsDesktopWeb search
Verification
L4 · Install tested
Failed
Risk
LowRisk
Health
Active
Trust
Silver

Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →

Install verification badge dsh 0.1.7-rc.1Install verification badge dsh 0.1.5-rc.2Install verification badge dsh 0.1.5-rc.1Install verification badge dsh 0.1.2-rc.1

What it doesAI

Displays the installed dsh version above the sidebar Settings button in DeepSeek Harness Web.

  • Shows installed dsh version
  • Positioned above sidebar Settings button
  • Designed for DeepSeek Harness Web
uiAI

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 @hjj345345/dsh-sm-version-display
verified 1.2.24

Install method: npm · sandbox install ok, web smoke failed (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 · peerDependenciesdeclared in 1.2.24
supports any of: dsh 0.1.x or dsh 0.2.x

Based on 1 requirement(s) across 2 @deepseek-ai/dsh-* packages.

raw ranges^0.1.7-rc.1 || ^0.2.0-rc.1 ×2

✓ Running dsh 0.2.1-rc.2 is within the declared range — install is not blocked by version.

Footnote: the author also wrote engines.dsh = ">=0.1.7-rc.1 || >=0.2.0-rc.1" — DSH does not read that field (not part of the verdict).

Whether it actually runs is a separate question → see the measured matrix below (L1–L5).

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)
At-a-glance → evidence in the cards below
plugin \ dshdsh 0.2.1-rc.2
current
dsh 0.2.1-alpha.4dsh 0.2.1-alpha.2dsh 0.2.0-rc.2dsh 0.1.7-rc.2
1.2.26·····
1.2.25·····
1.2.24✗✗✗✗·
1.2.20·····
1.2.19·····
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
1.2.26npm2026-10-24

@hjj345345/dsh-sm-version-display

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

1.2.25npm2026-10-22

@hjj345345/dsh-sm-version-display

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

1.2.24npm5 failed2026-10-18

@hjj345345/dsh-sm-version-display

✗dsh 0.2.1-rc.2current2026-10-18L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-rc.2
  • • Plugin artifact: npm · @hjj345345/dsh-sm-version-display@1.2.24
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
Failed
Sandbox install failed
L5 · failed

ID: dsh-sm-version-display@1.2.24@dsh0.2.1-rc.2 · profile: l4-sandbox

Issued: 2026-10-18 · expires: 2026-10-25

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-24
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-24
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18
spec @hjj345345/dsh-sm-version-display · channel npm package · outcome ran · exit 0
check took: 3.3s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18
spec @hjj345345/dsh-sm-version-display · channel npm package · outcome ran · exit 0
check took: 3.3s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18
spec @hjj345345/dsh-sm-version-display · channel npm package · outcome ran · exit 0
check took: 3.3s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18
spec @hjj345345/dsh-sm-version-display · install mode reused L4 scratch
check took: 0ms
Web boot ready✕ Failed
plugin tree failed to load
HTTP endpoint served✕ Failed

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
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-alpha.4
  • • Plugin artifact: npm · @hjj345345/dsh-sm-version-display@1.2.24
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
Failed
Sandbox install failed
L5 · failed

ID: dsh-sm-version-display@1.2.24@dsh0.2.1-alpha.4 · profile: l4-sandbox

Issued: 2026-10-16 · expires: 2026-10-23

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-24
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-24
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-16
spec @hjj345345/dsh-sm-version-display · channel npm package · outcome ran · exit 0
check took: 4.5s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-16
spec @hjj345345/dsh-sm-version-display · channel npm package · outcome ran · exit 0
check took: 4.5s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-16
spec @hjj345345/dsh-sm-version-display · channel npm package · outcome ran · exit 0
check took: 4.5s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-16
spec @hjj345345/dsh-sm-version-display · install mode reused L4 scratch
check took: 0ms
Web boot ready✕ Failed
plugin tree failed to load
HTTP endpoint served✕ Failed

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-10L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-alpha.2
  • • Plugin artifact: npm · @hjj345345/dsh-sm-version-display@1.2.24
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
Failed
Sandbox install failed
L5 · failed

ID: dsh-sm-version-display@1.2.24@dsh0.2.1-alpha.2 · profile: l4-sandbox

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

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-24
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-24
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-10
spec @hjj345345/dsh-sm-version-display · channel npm package · outcome ran · exit 0
check took: 4.4s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-10
spec @hjj345345/dsh-sm-version-display · channel npm package · outcome ran · exit 0
check took: 4.4s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-10
spec @hjj345345/dsh-sm-version-display · channel npm package · outcome ran · exit 0
check took: 4.4s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-10
spec @hjj345345/dsh-sm-version-display · install mode reused L4 scratch
check took: 0ms
Web boot ready✕ Failed
boot failed
HTTP endpoint served✕ Failed

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 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.0-rc.2
  • • Plugin artifact: npm · @hjj345345/dsh-sm-version-display@1.2.24
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
Failed
Sandbox install failed
L5 · failed

ID: dsh-sm-version-display@1.2.24@dsh0.2.0-rc.2 · profile: l4-sandbox

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

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-24
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-24
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-08
spec @hjj345345/dsh-sm-version-display · channel npm package · outcome ran · exit 0
check took: 5.6s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-08
spec @hjj345345/dsh-sm-version-display · channel npm package · outcome ran · exit 0
check took: 5.6s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-08
spec @hjj345345/dsh-sm-version-display · channel npm package · outcome ran · exit 0
check took: 5.6s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-08
spec @hjj345345/dsh-sm-version-display · install mode reused L4 scratch
check took: 0ms
Web boot ready✕ Failed
boot failed
HTTP endpoint served✕ Failed

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

✗prehistory2026-09-30L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: unknown
  • • Plugin artifact: npm · @hjj345345/dsh-sm-version-display@1.2.24
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
Failed
Sandbox install failed
L5 · failed

ID: dsh-sm-version-display@1.2.24@dshunknown · profile: l3-fullscan

Issued: 2026-09-30 · expires: 2026-10-07

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-24
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-24
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-30
spec @hjj345345/dsh-sm-version-display · channel npm package · install mode reused L4 scratch
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-30
spec @hjj345345/dsh-sm-version-display · channel npm package · install mode reused L4 scratch
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-30
spec @hjj345345/dsh-sm-version-display · channel npm package · install mode reused L4 scratch
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-30
spec @hjj345345/dsh-sm-version-display · install mode reused L4 scratch
check took: 0ms
Web boot ready✕ Failed
plugin tree failed to load
HTTP endpoint served✕ Failed

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

1.2.20npm2026-09-29

@hjj345345/dsh-sm-version-display

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

1.2.19npm2026-09-26

@hjj345345/dsh-sm-version-display

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

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:

dsh.so risk
`[![dsh.so risk](https://www.dsh.so/badge/dsh-sm-version-display.svg)](https://www.dsh.so/artifact/dsh-sm-version-display/)`
dsh 0.1.7-rc.1 install verified
`[![dsh.so install · dsh 0.1.7-rc.1](https://www.dsh.so/badge/install/dsh-sm-version-display@0.1.7-rc.1.svg)](https://www.dsh.so/artifact/dsh-sm-version-display/)`
dsh 0.1.5-rc.2 install verified
`[![dsh.so install · dsh 0.1.5-rc.2](https://www.dsh.so/badge/install/dsh-sm-version-display@0.1.5-rc.2.svg)](https://www.dsh.so/artifact/dsh-sm-version-display/)`
dsh 0.1.5-rc.1 install verified
`[![dsh.so install · dsh 0.1.5-rc.1](https://www.dsh.so/badge/install/dsh-sm-version-display@0.1.5-rc.1.svg)](https://www.dsh.so/artifact/dsh-sm-version-display/)`
dsh 0.1.2-rc.1 install verified
`[![dsh.so install · dsh 0.1.2-rc.1](https://www.dsh.so/badge/install/dsh-sm-version-display@0.1.2-rc.1.svg)](https://www.dsh.so/artifact/dsh-sm-version-display/)`

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-sm-version-displayAutomated review · daily

Static low; dynamic low (authoritative when present) → overall low.

static low→dynamic low→overall low
dynamic findings0 critical·0 high·0 medium·4 low
lowoverall · low
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
plugin versionv1.2.26dsh manifest
scanned version1.2.26npm2026-10-24
current version1.2.26same version
vet verdictclean · npm

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

show static findings (9)
  • warningchildProcess · code-execlib/index.js:566

    const child = spawn(process.execPath, [join(job.runtimeDir, 'update-worker.mjs'), "--state", UPDATE_STATE_FILE, '--job', job.id], { stdio: "

  • warningchildProcess · code-execlib/index.js:784

    const child = spawn(process.execPath, [join(next.runtimeDir, 'update-worker.mjs'), "--state", UPDATE_STATE_FILE, '--job', state.id, "--actio

  • warningchildProcess · code-execlib/update-runtime.mjs:90

    const child = spawn(ps, ['-NoProfile', '-NonInteractive', '-EncodedCommand', encode(bootstrap)], { windowsHide: true, stdio: ['ignore', 'pip

  • warningchildProcess · code-execlib/update-runtime.mjs:136

    const child = spawn(process.execPath, workerArgs, { detached: true, windowsHide: true, stdio: ['ignore', 'pipe', 'pipe'], shell: false });

  • warningchildProcess · code-execlib/update-worker.mjs:157

    const parentCode = `const child = require('node:child_process').spawn(${JSON.stringify(process.execPath)}, ['-e', ${JSON.stringify(childCode

  • warningchildProcess · code-execlib/update-worker.mjs:158

    const parent = spawn(process.execPath, ["-e", parentCode], { stdio: ["ignore", "ignore", "ignore", "ipc"], windowsHide: true });

  • warningchildProcess · code-execlib/update-worker.mjs:394

    const child = spawn(runnable.executable, runnable.args, { cwd, windowsHide: true, stdio: ["ignore", "pipe", "pipe"], shell: false });

  • warningshellExec · shelllib/update-worker.mjs:280

    const directory = execFileSync("powershell.exe", ["-NoProfile", "-NonInteractive", "-Command", "[bool]((Get-Item -LiteralPath $env:DSH_BACKU

  • warningshellExec · shelllib/update-worker.mjs:358

    execFileSync(join(process.env.SystemRoot ?? "C:\\Windows", "System32", "taskkill.exe"), ["/PID", String(child.pid), "/T", "/F"], { stdio: "i

2model reads redacted source context · never executes plugin code
highest gradelow
merged intooverall low
audited at2026-10-23
findings0 critical·0 high0 medium / 4 low hidden
show 4 audit findings
  • lowDesktop one-click update downloads and launches an installer binarylib/update-worker.mjs

    A compromised GitHub release asset or CDN response would result in arbitrary code running as the user. Mitigated: https-only, host whitelist, extension check, post-redirect re-validation, desktop-mode only, explicit user confirmation, and target version must match the registry check.

  • lowAuthenticated /directories route lists arbitrary filesystem directorieslib/index.js

    Any caller holding the page token can enumerate directory names anywhere the process can read (not file contents). Requires loopback + token + loopback Origin, so impact is limited to local disclosure of filesystem layout/usernames.

  • lowOrigin check accepts absent and literal "null" origins, leaving the bearer token as sole CSRF barrierlib/index.js

    A sandboxed iframe or non-browser client presenting Origin: null (or none) passes the origin gate; only the 64-hex page token prevents abuse, so any token leak (e.g. another plugin's client code reading window.__DSH_UPDATE_TOKEN__) becomes directly exploitable for update/backup/delete actions.

  • lowBackup copies the whole DSH home and global install into a caller-chosen directorylib/update-worker.mjs

    ~/.dsh (which can hold other plugins' settings/credentials) and the full global install are copied to a user-selected path; if that path is cloud-synced or world-readable, secrets leave the machine. Chosen by the local user via UI, and only excluded paths are blocked by the unaudited validateBackupDirectory.

No critical/high risk: update endpoints are loopback+token+origin gated, child processes run with shell:false and strictly validated versions; only low-impact hardening gaps remain.

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

• Repo created: 2026-08-28

• Stars: ★ 1 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/hjj345/dsh-sm-version-display

Was this page helpful?