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
DSH development guard plugin with rolling snapshots, auto-rollback on failure, and a local management panel.
- Rolling snapshots keep recent N copies with timestamps and reasons.
- Auto-rollback to last good snapshot on plugin failure within guardrails.
- Local management panel/API for status, snapshots, rollback, and restore.
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:x2802490130-prog/dsh-guard#v1.0.0Install 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.
8 samples (roughly every 7 days), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-05 · 8 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-02 → 11-05 · 7 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 |
|---|---|---|---|---|---|
| v1.0.0 | ✓ | ✓ | ✓ | ✓ | ✓ |
v1.0.0github✓ 15 runtime-verified2026-11-15
https://github.com/x2802490130-prog/dsh-guard
✓dsh 0.2.2-rc.3current2026-11-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/x2802490130-prog/dsh-guard#v1.0.0
ID: dsh-guard@v1.0.0@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-15 · expires: 2026-11-22
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-06L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/x2802490130-prog/dsh-guard#v1.0.0
ID: dsh-guard@v1.0.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-06 · expires: 2026-11-13
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.52026-10-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/x2802490130-prog/dsh-guard#v1.0.0
ID: dsh-guard@v1.0.0@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-28L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/x2802490130-prog/dsh-guard#v1.0.0
ID: dsh-guard@v1.0.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-28 · expires: 2026-11-04
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-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/x2802490130-prog/dsh-guard#v1.0.0
ID: dsh-guard@v1.0.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-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.2.1-alpha.22026-10-12L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/x2802490130-prog/dsh-guard#v1.0.0
ID: dsh-guard@v1.0.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
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-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/x2802490130-prog/dsh-guard#v1.0.0
ID: dsh-guard@v1.0.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-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.7-rc.22026-09-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/x2802490130-prog/dsh-guard#v1.0.0
ID: dsh-guard@v1.0.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-27 · expires: 2026-10-04
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.12026-09-23L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/x2802490130-prog/dsh-guard#v1.0.0
ID: dsh-guard@v1.0.0@dsh0.1.7-rc.1 · profile: l3-fullscan
Issued: 2026-09-23 · expires: 2026-09-30
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/x2802490130-prog/dsh-guard#v1.0.0
ID: dsh-guard@v1.0.0@dsh0.1.6-alpha.2 · profile: l3-fullscan
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/x2802490130-prog/dsh-guard#v1.0.0
ID: dsh-guard@v1.0.0@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/x2802490130-prog/dsh-guard#v1.0.0
ID: dsh-guard@v1.0.0@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/x2802490130-prog/dsh-guard#v1.0.0
ID: dsh-guard@v1.0.0@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/x2802490130-prog/dsh-guard#v1.0.0
ID: dsh-guard@v1.0.0@dsh0.1.3-alpha.1 · profile: l4-sandbox
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-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/x2802490130-prog/dsh-guard#v1.0.0
ID: dsh-guard@v1.0.0@dshunknown · profile: l3-fullscan
Issued: 2026-09-30 · expires: 2026-10-07
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-guard/?ref=badge)``[](https://www.dsh.so/artifact/dsh-guard/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-guard/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-guard/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-guard/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-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.
v1.0.0dsh manifestv1.0.0git2026-11-17v1.0.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (2)
- criticalspawnShell · shell
lib/index.js:262try { spawn(config.restartCommand, [], { detached: true, stdio: 'ignore', shell: true }).unref() } catch { /* */ } - warningnetIp · network
lib/index.js:351log('管理面板已挂载: http://127.0.0.1:<port>/dsh-guard')
show 3 audit findings
- mediumAdmin API trusts only the TCP peer address; no Host/Origin validation on the 'loopback only' endpoints
lib/index.js:143Every /api/dsh-guard/* and /dsh-guard handler is gated solely by this socket-address test (guardAdmin → isLoopback). Any request that reaches the harness webServer from a local peer is accepted unauthenticated: a reverse proxy or tunnel (cloudflared/ngrok style) that connects from 127.0.0.1, or a DNS-rebinding page whose port matches, can call POST /rollback or /restore to overwrite live files in the DSH profile/home (cordis.patch.yml, settings.yaml, .credentials.yaml, package.json) with older snapshot content, trigger /save, modify guard-config.json, and read the guard log.
- lowrestartCommand is executed via shell:true, but is only reachable from trusted host config
lib/index.js:262This is the construct a heuristic scanner flags as critical (arbitrary command execution). Reachability analysis shows it is not remotely controllable: the value is read from config.restartCommand (the plugin row config supplied in the harness/cordis config), not from the merged file config; guard-config.json, which the HTTP API can write, is merged only into graceMs/autoSaveDelayMs/keepSnapshots/eventSaveDelayMs/eventMinIntervalMs, so a network caller cannot set restartCommand. It additionally requires a plugin run failure inside graceMs with a last-good snapshot older than the current boot.
- low~/.dsh/.credentials.yaml is copied into every snapshot, last-good mirror and pre-rollback backup
lib/index.js:42The credential file is duplicated by design into snapshots/<ts>, snapshots/last-good and backups/<ts>-pre-*, and copies survive credential rotation until the rolling prune removes them (keepSnapshots, 1-20, plus all backups). A rollback or restore can reinstate an older, potentially revoked credentials file over the live one, and any later archive/sync of ~/.dsh/snapshots carries the secrets. No exfiltration path was found: no route serves snapshot file contents (GET /log returns only guard.log lines).
Flagged shell spawn is gated behind trusted row config restartCommand; residual risk is the loopback-only admin API trusting only the TCP peer address, not Host/Origin.
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-15 · activity: Inactive
• Repo created: 2026-08-15
• Stars: ★ 0 · Forks: 0
• 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-guard?
dsh-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-guard?
Run dsh plugin --profile web add github:x2802490130-prog/dsh-guard#v1.0.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-17 (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.
