Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.3 · 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
Safety net for plugin installs: snapshots, rollback, guarded boot, and incident reports with agent analysis.
- Pre-install snapshots and backup
- One-click or automatic rollback
- Incident reports auto-trigger agent analysis
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 github:lxzy-7/dsh-plugin-guard#v0.3.2Install method: GitHub · runtime verified (L5)
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.
7 samples (roughly every 7 days), 2 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-13 · 7 points
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-01 → 11-13 · 6 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
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
Only 0 points (< 3): no chart yet
no data yet
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.2-rc.3 current | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| v0.3.2 | ✓ | ✓ | ✓ | ✓ | ✓ |
v0.3.2github✓ 16 runtime-verified2026-11-16
https://github.com/lxzy-7/dsh-plugin-guard
✓dsh 0.2.2-rc.3current2026-11-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/lxzy-7/dsh-plugin-guard#v0.3.2
ID: dsh-plugin-guard@v0.3.2@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-16 · expires: 2026-11-23
View checks & evidence
active in loader tree (206 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.2-rc.12026-11-13L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/lxzy-7/dsh-plugin-guard#v0.3.2
ID: dsh-plugin-guard@v0.3.2@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-13 · expires: 2026-11-20
View checks & evidence
active in loader tree (200 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.1-rc.52026-10-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/lxzy-7/dsh-plugin-guard#v0.3.2
ID: dsh-plugin-guard@v0.3.2@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-30 · expires: 2026-11-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.2.1-rc.32026-10-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/lxzy-7/dsh-plugin-guard#v0.3.2
ID: dsh-plugin-guard@v0.3.2@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
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-rc.22026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/lxzy-7/dsh-plugin-guard#v0.3.2
ID: dsh-plugin-guard@v0.3.2@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
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-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/lxzy-7/dsh-plugin-guard#v0.3.2
ID: dsh-plugin-guard@v0.3.2@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-15 · expires: 2026-10-22
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.22026-10-10L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/lxzy-7/dsh-plugin-guard#v0.3.2
ID: dsh-plugin-guard@v0.3.2@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-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.2.0-rc.22026-10-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/lxzy-7/dsh-plugin-guard#v0.3.2
ID: dsh-plugin-guard@v0.3.2@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: github · https://github.com/lxzy-7/dsh-plugin-guard#v0.3.2
ID: dsh-plugin-guard@v0.3.2@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-25L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/lxzy-7/dsh-plugin-guard#v0.3.2
ID: dsh-plugin-guard@v0.3.2@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
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: github · https://github.com/lxzy-7/dsh-plugin-guard#v0.3.2
ID: dsh-plugin-guard@v0.3.2@dsh0.1.6-alpha.2 · profile: l4-sandbox
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-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/lxzy-7/dsh-plugin-guard#v0.3.2
ID: dsh-plugin-guard@v0.3.2@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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-13L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/lxzy-7/dsh-plugin-guard#v0.3.2
ID: dsh-plugin-guard@v0.3.2@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-13 · expires: 2026-09-20
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-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/lxzy-7/dsh-plugin-guard#v0.3.2
ID: dsh-plugin-guard@v0.3.2@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-16
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.12026-09-07L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/lxzy-7/dsh-plugin-guard#v0.3.2
ID: dsh-plugin-guard@v0.3.2@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
active in loader tree (151 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓prehistory2026-10-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/lxzy-7/dsh-plugin-guard#v0.3.2
ID: dsh-plugin-guard@v0.3.2@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
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 dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/dsh-plugin-guard/?ref=badge)``[](https://www.dsh.so/artifact/dsh-plugin-guard/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-plugin-guard/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-plugin-guard/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-plugin-guard/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-plugin-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.3.2dsh manifestv0.3.2git2026-11-16v0.3.2same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningnetIp · network
scripts/boot-guard.sh:35healthy() { curl -fsS --max-time 3 "http://127.0.0.1:$PORT/" >/dev/null 2>&1; } - warningnetIp · network
scripts/guard-cli.js:149console.log(`http://127.0.0.1:${port}/ -> ${healthy ? '正常' : '异常'}`) - warningchildProcess · code-exec
src/engine.js:262? spawnSync('cmd.exe', ['/d', '/s', '/c', 'pnpm --version'], { encoding: 'utf8' }) - warningchildProcess · code-exec
src/engine.js:263: spawnSync('pnpm', ['--version'], { encoding: 'utf8' }) - warningchildProcess · code-exec
src/engine.js:289? spawnSync( - warningnetIp · network
src/incident.js:171lines.push(`- 健康状态: http://127.0.0.1:${port}/ -> ${healthy ? '正常' : '异常'}`)
show 4 audit findings
- mediumState-mutating /guard/api routes accept any caller with no auth, origin or CSRF check
src/index.js:182The handlers never inspect method, Origin, Referer, token or user; readBody parses JSON from any body, so a simple (preflight-free) cross-origin POST to http://127.0.0.1:<port>/guard/api/... from any web page the user visits, or from any local process, reaches them. Concretely: POST /guard/api/booted sets guardClientBooted=true (src/index.js:124) and thereby spoofs the black-screen/heartbeat signal the boot guard is meant to gate rollback on; /guard/api/keep rewrites the retention config; /guard/api/snapshot forces snapshots (and pruning of older ones); /guard/api/rollback restores profile fil
- lowIncident prompt text is built verbatim from a writable marker file and log-derived report, at system-prompt priority -50
src/incident.js:118incidentSectionText() interpolates inc.kind, inc.time, inc.report, inc.pluginId and inc.pluginName, read from $DSH_HOME/guard/pending-incident.json, into a host-authored instruction block registered as systemPrompt section order -50 (src/index.js:149-153). Any writer of that file (the CLI, another plugin sharing DSH_HOME, or crafted `--kind`/tool arguments) therefore places arbitrary text ahead of the persona, and the referenced report embeds raw boot/server log tails (buildIncidentReport), so log content also reaches the model as instructions. The ${id} is additionally echoed into a shell-loo
- lowHTTP-supplied profile/stamp strings are joined into snapshot and restore paths without validation
src/index.js:75profileDir/rollbacksRoot are plain join() calls (src/layout.js: profileDir(name) => join(profilesDir(), name)), so a body.profile containing '../' segments escapes $DSH_HOME/profiles and $DSH_HOME/rollbacks; snapshotProfile then mkdir's the escaped snapshot dir and copies the five SNAPSHOT_FILES there, and handleRollback/restoreSnapshot can copy those same fixed filenames into any escaped directory. Combined with the unauthenticated route this turns into a constrained arbitrary-directory create/overwrite primitive (only package.json, pnpm-lock.yaml, pnpm-workspace.yaml, cordis.yml, cordis.patc
- lowQuarantine writes the plugin id into cordis.patch.yml via raw string interpolation
src/engine.js:154id is interpolated into YAML without quoting/escaping. It normally comes from a patch row (profilePluginRows) or the CLI --plugin check, but an id string that itself contains newlines/YAML structure (e.g. a block-scalar id in a plugin's cordis.patch.yml) produces extra patch entries — enabling/disabling other rows or injecting arbitrary profile composition entries — the next time the profile boots. Requires write access to the profile's patch file or CLI use.
Purpose-fit snapshot/rollback plugin; no RCE or exfiltration, but unauthenticated /guard/api routes mutate local install state and a marker file is injected into the system prompt.
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-18 · activity: Inactive
• Repo created: 2026-08-16
• Stars: ★ 43 · Forks: 3
• Health: Inactive — no commit in 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).
Frequently asked questions
What is dsh-plugin-guard?
dsh-plugin-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-plugin-guard?
Run dsh plugin --profile web add github:lxzy-7/dsh-plugin-guard#v0.3.2 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-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.
