Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →
Showing badges for the 5 most recent dsh versions; older ones are hidden.
Data as of (UTC)
What it doesAI
Pre-execution safety gate for DSH that statically and semantically screens bash/pwsh commands, allowing, fixing, blocking, or escalating risky operations.
- Static rules plus TypeSafe Jev semantic verdicts before any bash/pwsh run
- Four-way handling: allow, correct, block, or escalate to human review
- Quota-based degradation and audit logging of every decision
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.
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); the npm pair from every snapshot.
8 samples (roughly every 7 days), 4 of them reconstructed (hollow dots); sampled points, not a daily series
09-22 → 11-03 · 8 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-02 → 11-03 · 7 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-22 → 11-03 · 40 points
The snapshot’s last-week rolling window (official npm + npmmirror combined)
09-22 → 11-04 · 41 points
Installation
dsh plugin --profile web add dsh-jev-guardInstall method: GitHub · runtime verified (L5) · verified on dsh 0.2.1-rc.5
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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin ＼ dsh | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| 0.5.7 | ✓ | ✓ | · | · | · |
| 0.5.6 | · | · | ✓ | · | · |
| 0.5.5 | · | · | · | ✓ | · |
| 0.5.4 | · | · | · | · | ✓ |
| 0.5.3 | · | · | · | · | · |
0.5.7npm✓ 2 runtime-verified2026-11-04
dsh-jev-guard
✓dsh 0.2.1-rc.52026-11-01L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · dsh-jev-guard@0.5.7
ID: dsh-jev-guard@0.5.7@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
View checks & evidence
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
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-rc.32026-10-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-jev-guard@0.5.7
ID: dsh-jev-guard@0.5.7@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
View checks & evidence
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
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.5.6npm✓ 1 runtime-verified2026-10-20
dsh-jev-guard
✓dsh 0.2.1-rc.22026-10-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-jev-guard@0.5.6
ID: dsh-jev-guard@0.5.6@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
View checks & evidence
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
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.5.5npm✓ 1 runtime-verified2026-10-18
dsh-jev-guard
✓dsh 0.2.1-alpha.42026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-jev-guard@0.5.5
ID: dsh-jev-guard@0.5.5@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
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.5.4npm✓ 3 runtime-verified2026-10-15
dsh-jev-guard
✓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-jev-guard@0.5.4
ID: dsh-jev-guard@0.5.4@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
View checks & evidence
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
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-jev-guard@0.5.4
ID: dsh-jev-guard@0.5.4@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
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-jev-guard@0.5.4
ID: dsh-jev-guard@0.5.4@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
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.5.3npm✓ 3 runtime-verified2026-09-30
dsh-jev-guard
✓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-jev-guard@0.5.3
ID: dsh-jev-guard@0.5.3@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
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-jev-guard@0.5.3
ID: dsh-jev-guard@0.5.3@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
View checks & evidence
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
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-jev-guard@0.5.3
ID: dsh-jev-guard@0.5.3@dshunknown · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-jev-guard@0.5.7@dsh0.2.2-rc.1 (l3-fullscan)
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 dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/dsh-jev-guard/?ref=badge)``[](https://www.dsh.so/artifact/dsh-jev-guard/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-jev-guard/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-jev-guard/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-jev-guard/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-jev-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.
Static low; dynamic medium (authoritative when present) → overall medium.
v0.5.0dsh manifestv0.5.0git2026-11-05v0.5.8version moved onclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (8)
- criticaldestructiveRm · destructive
tools/gate-cli.mjs:60['rm -rf /tmp/build-cache', true], - criticaldestructiveRm · destructive
tools/gate-cli.mjs:61['rm -rf /home/user/Photos/2024', false], - criticaldestructiveRm · destructive
tools/gate-cli.mjs:63['rm -rf /', false], - criticaldestructiveRm · destructive
tools/probe-scripts.mjs:75{ label: 'sudo rm -rf /var/lib/docker', command: 'sudo rm -rf /var/lib/docker' }, - criticaldestructiveRm · destructive
tools/smoke-dsh-adapter.mjs:133expect('非目标工具 → 放行', await handler({ ...fakeExec('rm -rf /home/user/x'), name: 'read' }, nextAllow), 'allow') - criticaldestructiveRm · destructive
tools/smoke-dsh-adapter.mjs:186await handlerNoKey(fakeExec('rm -rf /home/user/jev-guard-smoke-demo'), nextAllow), 'allow') - criticaldestructiveRm · destructive
tools/smoke-dsh-adapter.mjs:256const destructive = await h(neverExec('rm -rf ~/dsh-cross-search'), nextAllow) - criticaldestructiveRm · destructive
tools/smoke-dsh-pipeline.mjs:113const live = await run(ctx, 'rm -rf ~/dsh-cross-search')
show 4 audit findings
- mediumGated command text and enriched script bodies leave the machine unmasked to api.typesafe.ai
tools/probe-scripts.mjs:92The plugin's core function ships the full command string to a third-party classifier, and with inlineScripts:true (default in cordis.patch.yml) also the body of referenced script files, read from disk. Unlike the audit log, this outbound path is not masked: lib/audit.js explicitly notes '命令文本可能内联密钥(实测你的历史里有这种写法)' and masks before writing, while the request payload carries the raw text. A command such as `DEEPSEEK_API_KEY=sk-... node x.mjs` therefore sends the live key to api.typesafe.ai. The sensitive-path skip list for script bodies lives in lib/gate.js, which was not harvested, so its effect
- lowAudit log persists full commands with prefix-only masking and default file permissions
lib/audit.js:95Every gated command is appended to ~/.jev-guard/guard.log (default mode from appendFile, typically 0644). Masking only recognizes a fixed prefix set (`sk|ghp|glpat|tvly|xoxb|as_sk|apikey...`), so credentials in other shapes — `mysql -u root -pS3cret`, `--token=...`, bearer headers, basic-auth URLs — are stored in clear and readable by other local users.
- lowOffline harvester reads the user's full bash history and DSH session command logs
tools/extract-commands.mjs:92harvest() walks ~/.dsh/sessions for every session.jsonl.zstd.dec and parses all tool/call bash commands, plus ~/.bash_history. Combined with `gate-cli.mjs --sessions`, this bulk command corpus (potentially containing inline credentials and private paths) is uploaded to api.typesafe.ai. It is a manually invoked developer tool, not runtime code, which caps the severity.
- lowTest harness imports an arbitrary module path taken from JEV_GUARD_ROOT
tools/smoke-dsh-pipeline.mjs:74If JEV_GUARD_ROOT is attacker-influenced (shared shell profile, CI variable), the harness executes attacker code under the developer's account. It is a manual test script outside the DSH runtime path, so impact is limited to developer machines.
Scanner criticals are unreachable probe fixtures; the real residual risk is that every gated command and script body is sent unmasked to api.typesafe.ai.
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-10-31 · activity: Active
• Repo created: 2026-09-20
• Stars: ★ 1 · Forks: 0
• Health: Active — committed within last 30 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).
Frequently asked questions
What is @7starsseeker/dsh-jev-guard?
@7starsseeker/dsh-jev-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 @7starsseeker/dsh-jev-guard?
Run dsh plugin --profile web add github:7starsseeker/dsh-jev-guard#v0.5.0 in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4) plus web smoke testing (L5).
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-11-05 (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.