The original repository has been deleted or made private. This page is an archival snapshot from indexing time; the install command may no longer work.

dsh-poison-guard avatar

dsh-poison-guard

Pre-install supply-chain poison scanner for DeepSeek Harness plugins: AST (JS-X-Ray) + deobfuscation + regex. Catches obfuscated exfiltration, eval, hidden shell commands.

PluginSecurityDeveloperTerminalCode reviewTerminal / Shell
Verification
L4 · Install tested
stale
Risk
Out of scope
Health
Inactive
Trust
Silver

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

Install verification badge dsh 0.1.3-alpha.1Install verification badge dsh 0.1.2-alpha.1

Data as of (UTC)

What it doesAI

Pre-install supply-chain poison scanner for DeepSeek Harness plugins using AST analysis and deobfuscation to catch malicious code.

  • Uses AST analysis via JS-X-Ray
  • Detects obfuscated exfiltration and eval
  • Identifies hidden shell commands
securityAIcode-reviewAI

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-poison-guard
tested artifact 0.2.0

Install method: npm · sandbox install ok, web smoke failed (L5) · verified on dsh 0.2.1-alpha.2

Trends

Four lines, four questions: total stars, stars gained this week, cumulative downloads, downloads this week. The GitHub pair comes from real-read sampling — a rotating daily shard, so one plugin is re-read roughly every 5–14 days, sparser than npm; the npm pair has a value on every snapshot day. The two cumulative panels are smoothed curves with no sample markers; the two weekly panels keep their raw bars and add a 4-week moving-average trend line that strips single-week noise down to the direction of travel.

GitHub stars
1★

5 samples (roughly every 1 days), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series

09-18 → 10-12 · 5 points

Weekly star gain
+0★

Bars = the delta between two samples 5–14 days apart (negative points down, faint bars contain reconstructed points); line = 4-week moving-average trend

10-02 → 10-12 · 4 points

Cumulative downloads
—

Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)

Only 0 points (< 3): no chart yet

no data yet

Weekly downloads
321

Bars = the snapshot’s last-week rolling window (official npm + npmmirror combined); line = 4-week moving-average trend — the shape of weekly demand, not a user count

08-19 → 10-12 · 46 points

npm snapshots 80 · 46 observed days · mirror included from 2026-10-18weekly board —total board —downloads ≠ unique usersstar weekly —

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
only dsh 0.1.x (0.1.0-rc.6 and up, below 0.2.0)

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

raw ranges^0.1.0-rc.6 ×1

✗ Running dsh 0.2.2-rc.3 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-poison-guard@0.2.0 0.2.2-rc.3 (the exemption lives in the local profile; this site does not assume one)

Deciding channel: no engines.dsh declared, so every dsh* peer is checked (workspace:^ | ~ | * counts as the running version).

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-alpha.2dsh 0.2.0-rc.2dsh 0.1.7-rc.2dsh 0.1.7-rc.1dsh 0.1.7-alpha.2
0.2.0✗✗✗✗✗
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
0.2.0npm✓ 1 runtime-verified11 failed2026-10-12

dsh-poison-guard

✗dsh 0.2.1-alpha.22026-10-12L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-alpha.2
  • • Plugin artifact: npm · dsh-poison-guard@0.2.0
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-poison-guard@0.2.0@dsh0.2.1-alpha.2 · profile: l4-sandbox

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

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-10
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-10
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-12
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 4.3s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-12
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 4.3s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-12
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 4.3s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-12
spec dsh-poison-guard · 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.0-rc.22026-10-09L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.0-rc.2
  • • Plugin artifact: npm · dsh-poison-guard@0.2.0
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-poison-guard@0.2.0@dsh0.2.0-rc.2 · profile: l4-sandbox

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

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-10
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-10
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-09
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 15.0s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-09
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 15.0s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-09
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 15.0s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-09
spec dsh-poison-guard · 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.1.7-rc.22026-09-26L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.7-rc.2
  • • Plugin artifact: npm · dsh-poison-guard@0.2.0
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-poison-guard@0.2.0@dsh0.1.7-rc.2 · profile: l4-sandbox

Issued: 2026-09-26 · expires: 2026-10-03

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-10
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-10
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-26
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 5.2s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-26
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 5.2s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-26
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 5.2s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-26
spec dsh-poison-guard · 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.1.7-rc.12026-09-24L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.7-rc.1
  • • Plugin artifact: npm · dsh-poison-guard@0.2.0
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-poison-guard@0.2.0@dsh0.1.7-rc.1 · profile: l4-sandbox

Issued: 2026-09-24 · expires: 2026-10-01

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-10
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-10
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-24
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 4.6s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-24
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 4.6s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-24
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 4.6s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-24
spec dsh-poison-guard · 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.1.7-alpha.22026-09-23L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.7-alpha.2
  • • Plugin artifact: npm · dsh-poison-guard@0.2.0
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-poison-guard@0.2.0@dsh0.1.7-alpha.2 · profile: l4-sandbox

Issued: 2026-09-23 · expires: 2026-09-30

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-10
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-10
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-23
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 5.7s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-23
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 5.7s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-23
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 5.7s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-23
spec dsh-poison-guard · 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.1.6-alpha.22026-09-20L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.6-alpha.2
  • • Plugin artifact: npm · dsh-poison-guard@0.2.0
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-poison-guard@0.2.0@dsh0.1.6-alpha.2 · profile: l3-fullscan

Issued: 2026-09-20 · expires: 2026-09-27

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-10
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-10
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-19
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 6.2s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-19
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 6.2s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-19
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 6.2s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-19
spec dsh-poison-guard · 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.1.6-alpha.12026-09-16L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.6-alpha.1
  • • Plugin artifact: npm · dsh-poison-guard@0.2.0
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-poison-guard@0.2.0@dsh0.1.6-alpha.1 · profile: l4-sandbox

Issued: 2026-09-16 · expires: 2026-09-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-10
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-10
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-16
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 6.1s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-16
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 6.1s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-16
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 6.1s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-16
spec dsh-poison-guard · 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.1.5-rc.22026-09-11L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.5-rc.2
  • • Plugin artifact: npm · dsh-poison-guard@0.2.0
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-poison-guard@0.2.0@dsh0.1.5-rc.2 · profile: l4-sandbox

Issued: 2026-09-11 · expires: 2026-09-18

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-10
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-10
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-11
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 9.0s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-11
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 9.0s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-11
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 9.0s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-11
spec dsh-poison-guard · 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.1.3-alpha.22026-09-08L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.3-alpha.2
  • • Plugin artifact: npm · dsh-poison-guard@0.2.0
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-poison-guard@0.2.0@dsh0.1.3-alpha.2 · profile: l4-sandbox

Issued: 2026-09-08 · expires: 2026-09-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-10
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-10
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-08
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 9.3s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-08
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 9.3s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-08
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 9.3s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-08
spec dsh-poison-guard · 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.1.3-alpha.12026-09-06L5 · runtime verified
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.3-alpha.1
  • • Plugin artifact: npm · dsh-poison-guard@0.2.0
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.1.3-alpha.1

ID: dsh-poison-guard@0.2.0@dsh0.1.3-alpha.1 · profile: l4-sandbox

Issued: 2026-09-06 · expires: 2026-09-13

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-10
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-10
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-06
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 6.1s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-06
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 6.1s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-06
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 6.1s
L5 · Run tested✓ Passed

active in loader tree (151 entries)

Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-06
spec dsh-poison-guard · install mode reused L4 scratch
check took: 104ms
Web boot ready✓ Passed
Source: DSH runtime · Method: web boot · Captured 2026-09-06
ready line dsh web: http://127.0.0.1:49785/?token=…
HTTP endpoint served✓ Passed
Source: DSH runtime · Method: HTTP request · Captured 2026-09-06
path / · HTTP 200 · took 104ms
Plugin active in inventory✓ Passed
Source: DSH runtime · Method: plugin inventory query · Captured 2026-09-06
verdict active · entries 151
match: include:poison-guard · dsh-poison-guard · phase active
phases: active 123 · null 28

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-05L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.2-rc.1
  • • Plugin artifact: npm · dsh-poison-guard@0.2.0
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-poison-guard@0.2.0@dsh0.1.2-rc.1 · profile: l3-fullscan

Issued: 2026-09-05 · expires: 2026-09-12

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-10
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-10
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-05
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 18.3s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-05
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 18.3s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-05
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 18.3s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-05
spec dsh-poison-guard · 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.

✗prehistory2026-10-05L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: unknown
  • • Plugin artifact: npm · dsh-poison-guard@0.2.0
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-poison-guard@0.2.0@dshunknown · profile: l4-sandbox

Issued: 2026-10-05 · expires: 2026-10-12

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-10
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-10
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-05
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 26.3s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-05
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 26.3s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-05
spec dsh-poison-guard · channel npm package · outcome ran · exit 0
check took: 26.3s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-05
spec dsh-poison-guard · 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.

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 dsh.so badges in your README to show this plugin's automated security-scan and install-test status:

dsh.so risk badge
`[![dsh.so risk](https://cdn.dsh.so/badge/dsh-poison-guard.svg)](https://www.dsh.so/artifact/dsh-poison-guard/?ref=badge)`
dsh 0.1.3-alpha.1 install verified
`[![dsh.so install · dsh 0.1.3-alpha.1](https://cdn.dsh.so/badge/install/dsh-poison-guard@0.1.3-alpha.1.svg)](https://www.dsh.so/artifact/dsh-poison-guard/?ref=badge-install)`
dsh 0.1.2-alpha.1 install verified
`[![dsh.so install · dsh 0.1.2-alpha.1](https://cdn.dsh.so/badge/install/dsh-poison-guard@0.1.2-alpha.1.svg)](https://www.dsh.so/artifact/dsh-poison-guard/?ref=badge-install)`

dsh.so is an independent community project, not affiliated with or endorsed by DeepSeek AI. Badges are maintained by dsh.so; embed links carry a ?ref= attribution parameter.

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-poison-guardAutomated review · daily

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

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

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

show static findings (3)
  • criticaleval · code-execlib/index.js:91

    'unsafe-stmt': 'dynamic code execution via eval() / Function() / vm',

  • criticalshellExec · shelllib/index.js:92

    'unsafe-command': 'shell command embedded in spawn()/exec()',

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

    'unsafe-command': 'shell command embedded in spawn()/exec()',

2model reads redacted source context · never executes plugin code
highest gradelow
merged intooverall low
audited at2026-10-16
audited artifactnpm 0.2.0
findings0 critical·0 high0 medium / 1 low hidden
show 1 audit findings
  • lowTool reads any caller-supplied absolute path with no workspace/plugin-root confinementlib/index.js:455

    The `path` parameter is documented as "Absolute path to the plugin directory" but is passed straight into collectFiles, which walks the tree (depth<=8), follows symlinks via statSync and readFileSync's every readable file under 2MB. Scan output returned into the model context includes rule hits, js-x-ray warning values (up to 240 chars) and deobfuscated fragments (up to 160 chars), so an agent steered by untrusted repository content could have the process read e.g. ~/.ssh, ~/.aws or /etc and surface partial content and path metadata. No data leaves the machine and nothing is executed or writte

Read-only static scanner: its 2 critical static hits are its own rule/regex literals; no runtime network, exec or env access. Only a low-risk unrestricted read path remains.

Rule (2026-10-28): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); the static scan tier (vet primary, dsh backstop) applies only when there is none (not queued / audit failed / withdrawn). 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 the static scan tier.

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-08-17 · activity: Inactive

• Repo created: 2026-08-16

• Stars: ★ 1 · Forks: 0

• Health: Inactive — no commit in 90+ days

Source

GitHub: github.com/zoahdev/dsh-poison-guard

Frequently asked questions

What is dsh-poison-guard?

dsh-poison-guard is a DeepSeek Harness (dsh) plugin listed on dsh.so — an independent community registry that indexes public source repositories and publishes automated security-scan and install-verification results for each entry.

Is dsh.so or this plugin page official?

dsh.so is an independent community registry and is not affiliated with, endorsed by, or sponsored by DeepSeek AI.

How do I install dsh-poison-guard?

Run dsh plugin --profile web add dsh-poison-guard in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4); the web smoke test (L5) has not passed yet.

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, so it can produce false positives and miss context. The model-driven dynamic security audit only covers plugins static-flagged at warn or above, never executes plugin code, and its conclusion is authoritative when there is one (it may raise or lower the static tier); exemptions stay manual. Neither layer is an endorsement: review the repository and the permissions it asks for before installing, together with the verification level and health signals.

How fresh is the data on this page?

The data on this page is as of 2026-10-16 (UTC) — the most recent valid timestamp among the registry refresh, install verification, security scan and dynamic audit. Build time is never used as a data date.

Was this page helpful?