dsh-secure-audit

dsh-secure-audit

English | 简体中文 Disclaimer. This is an unofficial third-party tool. It is not affiliated with, endorsed by, or sponsored by DeepSeek. "DeepSeek" and "DeepSeek Harness" are trademarks of their respective owners; they are referenced here only to describe what this plugin runs against.

Read-only security and compliance plugin for DeepSeek Harness (DSH).

Also listed in awesome-dsh-plugin · Awesome DeepSeek Harness Compatibility Peer dependency: @deepseek-ai/dsh-tools — the authoritative range is in package.json. It is optional, so installing the plugin never pulls a second copy of the DSH core tree. CI verifies the registration / execution / rendering contract against the real @deepseek-ai/dsh-tools at 0.1.0-rc.6, 0.1.2-rc.1, 0.1.7-rc.2, 0.2.0-rc.2, 0.2.1-rc.5 and 0.2.2-alpha.2 (job host-compat in ci.yml). DSH itself is pre-1.0: pin your DSH version and re-run security_audit after upgrading either side. No install-time scripts and no build step; the shipped source is the artifact.

Four tools and one skill: The plugin never writes, deletes, or executes anything on the audited system. That is a hard constraint of the codebase, not a convention: the audit/redaction/scan code paths perform reads only; the single write path in lib/ is the opt-in logFile audit log in lib/logger.js (append-only JSONL, disabled by default). Install

The plugin has no build step and no install scripts. index.js and lib/ are the shipped artifact; nothing compiles, so there is nothing to run at install time. npm: published — dsh plugin add dsh-secure-audit installs the latest release from the registry. The tarball attached to each GitHub release and the git source form below still work.

Notes for git installs: No prepare/postinstall scripts exist in this package, so nothing executes on your machine during install. pnpm ≥ 10 blocks lifecycle scripts of git dependencies by default. If a future version ever adds an install script, dsh will ask you to add the package to allowBuilds in the profile's pnpm-workspace.yaml, and it will run outside the agent sandbox. Review the source before approving. Pinning a commit (# ) prevents a later push from silently changing what runs. This is a security plugin; the maintainers' stance is that install-time code execution is an attack surface, so the package deliberately avoids it.

Dependency: @deepseek-ai/dsh-tools is a peer dependency supplied by the DSH runtime. lib/ itself imports only Node builtins. Release artifacts & integrity

Every GitHub release attaches the exact tarball its workflow built (npm pack, see release.yml); nothing is assembled by hand. Verify the file you install against the published hash before trusting it: Hashes are computed from the published GitHub release assets and updated with each release (see the release checklist). Git installs should pin a commit (# ) instead of a branch so the source cannot silently change. Usage Scan text for injection

Decisions: block — riskScore ≥ blockThreshold, or any critical rule hit. review — riskScore ≥ reviewThreshold; the pluggable classifier is consulted if configured. allow — nothing above reviewThreshold. allow means "no rule fired", not "safe".

Two numbers, two meanings: riskScore (0..1) is rule evidence only — the severity-weighted sum of matched rules. The model classifier never writes it. confidence is its deprecated alias, kept so 0.2.x consumers keep working. decisionConfidence (0..1) is certainty in the reported decision: the classifier's own confidence when it contributed, otherwise the rule score's support for the decision (riskScore for review/block, 1 − riskScore for allow). It is 0 when scanComplete is false.