@CetOeil/dsh-process-guard avatar

@CetOeil/dsh-process-guard

DeepSeek Harness plugin that refuses shell commands killing processes by image name, wildcard, process group, or unfiltered enumeration — the cleanup that closes the DSH GUI window.

PluginSecurityVisionTerminalDesktopTerminal / ShellVision / OCR
Verification
L5 · Run tested
Verified
Risk
LowRisk
Health
Active
Trust
Gold

Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →

Install verification badge dsh 0.2.1-rc.2

What it doesAI

Guard plugin that blocks shell commands killing processes by image name, wildcard, process group, or unfiltered enumeration.

  • Refuses kill commands targeting processes by image name
  • Blocks wildcard, process-group, and unfiltered process kills
  • Prevents accidental termination of the DSH GUI window
securityAIterminalAI

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-process-guard
verified 0.2.1

Install 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

Declared DSH compatibilityfrom package.json · peerDependencies
author declared no dsh version requirement

○ The author declares no dsh version requirement — install is not blocked by version.

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.2
0.2.1✓✓✗
v0.2.1···
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
0.2.1npm✓ 2 runtime-verified1 failed2026-10-20

dsh-process-guard

✓dsh 0.2.1-rc.2current2026-10-20L5 · runtime verified
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-rc.2
  • • Plugin artifact: npm · dsh-process-guard@0.2.1
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.2.1-rc.2

ID: dsh-process-guard@0.2.1@dsh0.2.1-rc.2 · profile: l4-sandbox

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

active in loader tree (150 entries)

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

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-18L5 · runtime verified
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-alpha.4
  • • Plugin artifact: npm · dsh-process-guard@0.2.1
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.2.1-alpha.4

ID: dsh-process-guard@0.2.1@dsh0.2.1-alpha.4 · 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-18
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-18
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18
spec dsh-process-guard · channel npm package · outcome ran · exit 0
check took: 2.2s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18
spec dsh-process-guard · channel npm package · outcome ran · exit 0
check took: 2.2s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18
spec dsh-process-guard · channel npm package · outcome ran · exit 0
check took: 2.2s
L5 · Run tested✓ Passed

active in loader tree (150 entries)

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

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-15L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-alpha.2
  • • Plugin artifact: npm · dsh-process-guard@0.2.1
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-process-guard@0.2.1@dsh0.2.1-alpha.2 · profile: l3-fullscan

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

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

v0.2.1github2026-10-14

https://github.com/CetOeil/dsh-process-guard

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

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-process-guard.svg)](https://www.dsh.so/artifact/dsh-process-guard/)`
dsh 0.2.1-rc.2 install verified
`[![dsh.so install · dsh 0.2.1-rc.2](https://www.dsh.so/badge/install/dsh-process-guard@0.2.1-rc.2.svg)](https://www.dsh.so/artifact/dsh-process-guard/)`

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

Static low, dynamic low — stricter wins → overall low.

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

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

show static findings (2)
  • criticalshellExec · shelllib/matcher.js:374

    if (/^find(?:\.exe)?\b/i.test(tail) && /-exec(?:dir)?$/i.test(tail)) return true;

  • warningnetIp · networklib/matcher.js:884

    return `process-guard: blocked - this terminates ${images} after selecting it by image name. That image may host the DSH GUI (http://127.0.0

2model reads redacted source context · never executes plugin code
highest gradelow
merged intooverall low
audited at2026-10-17
findings0 critical·0 high0 medium / 1 low hidden
show 1 audit findings
  • lowGuard's interpreter/wrapper denylist is incomplete, so some name-based kills pass uninspectedlib/matcher.js:76

    Indirect execution is only searched for executors and interpreters named in the enumerated lists (EXEC_WRAPPERS, INLINE_CODE_EXECUTABLES, INTERPRETER_EXECUTABLES). A payload inside an unlisted interpreter, e.g. `awk 'BEGIN{system("killall chrome")}'`, is hidden by the single-quote masking in maskViews() and matches no executor pattern, so evaluateCommand() returns allow and the protected image (browser / node harness host) can still be killed. This is a defense-in-depth gap in the plugin's own stated purpose, not a new capability for the attacker: it requires the caller to deliberately choose

No exploitable risk: this is a pure-text defensive guard with no network, filesystem or code-execution path; the static-scan hits are attack-signature strings used for detection.

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

• Repo created: 2026-09-21

• Stars: ★ 1 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/CetOeil/dsh-process-guard

Was this page helpful?