Pre-install static security review and runtime guard for dsh plugins: deobfuscation decoding, supply-chain checks, web one-click review/install/uninstall, and optional runtime tool-call guard.
Install
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:ateen18/dsh-plugin-security-review
Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).
README
简体中文 | English
Security review gate for dsh plugins — static pre-install vetting of malicious code, vulnerabilities and supply-chain risks (with deobfuscation decoding), runtime audit, optional tool-call guard, and a one-click review/install/uninstall panel.
Runs in both the web GUI and the dsh desktop client (desktop profile, dsh 0.2.x runtime bundled in Electron's app.asar). Desktop differences — built-in plugin-manager installs, no install-gate, policy stored by the plugin itself — are documented in the desktop adaptation notes.
A security review plugin for DeepSeek Harness (dsh) plugins. Once installed, every other plugin is statically reviewed before it is installed or loaded: dangerous code, vulnerabilities, and supply-chain risks are analyzed, a review report is produced, and an install recommendation is given. At runtime it keeps auditing the installed roster and disables dangerous plugins.
See README.md for the Chinese quick start (the repository's default README).
Full user guides:
- English: docs/USER_GUIDE.en.md
- 中文(简体): docs/使用说明.md
Three layers
| Layer | When | What it does |
|---|---|---|
| 1. Install gate | before install (dsh-safe-plugin add) |
downloads source without running any install scripts, analyzes it, prints the report; block refuses the install, warn needs confirmation, pass forwards to dsh plugin add --ignore-scripts |
| 2. Runtime gate | after dsh boots | audits every out-of-tree plugin in the profile (cached); blocked plugins are disabled via loader.update(id,{disabled:true}) and written into a managed disabled: true block in the profile's cordis.patch.yml, so their code is never imported on the next boot |
| 3. In-session tools | during sessions | security_review / security_review_status tools review any plugin/source directory and read historical reports |
Install
# From GitHub (recommended; the repo is cloned automatically)
dsh-safe-plugin add github:ateen18/dsh-plugin-security-review
# or: dsh plugin --profile web add github:ateen18/dsh-plugin-security-review
The package declares dsh.bundle, so the dsh plugin manager joins it into
dsh.profile.bundles automatically.
Install through an agent
You can also ask an agent inside a session instead of running the command yourself:
Install
github:ateen18/dsh-plugin-security-reviewinto the current profile (on the desktop client: thedesktopprofile).
The agent uses dsh's plugin_manager tool (install_bundle; the desktop client
executes it through the same built-in plugin manager as Settings → Plugins):
- The tool is enabled only in Creator (Cordis) mode; in Standard / PTC / Minimal
the agent falls back to running
dsh plugin … add(web) or the desktopdsh.cmd … add, which has the same effect. The 0.1.x web runtime has no such tool, so there the agent always uses the terminal. - The call requires full access (danger-full-access) or a per-call approval.
- If the package has install/build scripts, the agent first shows you the package
names awaiting approval (
pendingBuilds) and retries withapprovedBuildsonly after you agree. - Restart dsh (or wait for HMR) for the plugin to take full effect.
Letting an agent install a plugin means letting it download and run third-party code. Review it first with
dsh-safe-plugin review <target>, or use the "Review / safe install" panel of this plugin once it is installed.
dsh desktop client
The desktop client ships its runtime inside app.asar, uses the desktop
profile, and expects bundle operations to go through its built-in plugin
manager. Install it with the bundled CLI (adjust the path to your install):
& "$env:LOCALAPPDATA\Programs\DeepSeek Harness\resources\runtime\cli\bin\dsh.cmd" `
plugin --profile desktop add github:ateen18/dsh-plugin-security-review
Then restart the client (or let HMR hot-load it). Desktop differences:
install-gate is unavailable (the runtime is read-only), install/uninstall go
through the built-in pluginManager, and the policy is edited in this
plugin's own settings section. See
the desktop adaptation notes.
Review and install other plugins
dsh-safe-plugin add dsh-plugin-foo # review + install
dsh-safe-plugin add ./local-plugin-dir
dsh-safe-plugin add https://github.com/me/plugin.git
dsh-safe-plugin review dsh-plugin-foo # review only
dsh-safe-plugin review . --ignore test/fixtures # skip fixtures dirs
dsh-safe-plugin list # historical reports
dsh-safe-plugin verify # re-review installed plugins
Reports
- Score (0-100), verdict
pass / warn / block / audit, per-finding detail (severity, category, file:line, snippet, recommendation) and an install recommendation. - Persisted under
$DSH_HOME/security-review/:reports/latest/<name>.md(markdown),reports/history/*.json,index.json. - The web settings UI gains a
security-reviewsection (policy, auto-disable switch, allowlist).
Known limitations
- Static analysis cannot cover native binaries, runtime-downloaded code, or
heavily obfuscated payloads;
blockmeans strong risk signals, not proof of malice. - The runtime gate deterministically blocks plugin imports that happen after
this plugin applies; plugins that start earlier in the same boot batch
load for a few milliseconds before the boot audit disables them, and the
managed patch block keeps them from loading on the next boot. Use
dsh-safe-plugin addfor deterministic pre-install blocking. - Blocking a plugin that provides services other rows
injectfails boot loudly with the missing service named — that is dsh's fail-loud contract. - Transitive dependencies are checked by name heuristics only (no full source scan of the whole dependency tree).
- A review-engine failure degrades to
warn(fail-open) so the reviewer itself can never brick dsh; re-check withdsh-safe-plugin verify.
Development
npm test # analyzer unit tests (no dsh needed; run from this dir)
License: MIT
Links
More in this category
kenryu42/cc-safety-net★ 2082
Pre-execution guard that blocks destructive Git and filesystem commands and access to secrets such as SSH keys and .env files before a tool call runs.
ADWMC/helm-d#helmd★ 1413
Security-analysis plugin for DeepSeek Harness: 33 tools spanning six security domains, evidence/reporting and toolbox, plus the case lifecycle, routing and tool ledger; a session-bound case workflow with an evidence chain, E-id validation and reproducible findings; 362 on-demand references; three hot-swappable persona profiles; and a four-tab workbench (armor / case / intercept / about) with case-state recovery after context compaction.
toby-bridges/api-relay-audit★ 925
Runs local security audits of AI API relays and LLM proxies from DeepSeek Harness, producing Markdown reports for prompt injection, model substitution signals, tool-call rewriting, error leakage, stream integrity, and profile-gated Web3 risks.
SeaOf0/dsh-redteam-model★ 902
Authorized-security DSH collection: nine work modes (redteam coordinator, pentest, code audit, binary analysis, attack-defense, AV evasion, incident response, cloud security, CTF solving) and fifteen runtime plugins, managed from a settings page with one-click deploy, install, update and uninstall.
howmp/dsh-pentest★ 622
Authorized pentest mode for DeepSeek Harness — exploration chain, assets and findings with a Web view.
PerryLink/dsh-auto-review★ 253
Second-model auto-review on the approval answerer chain: a read-only reviewer subagent returns structured allow/deny verdicts with reasons, fail-closed by default.
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.