dsh-plugin-guard

The DeepSeek plugin ecosystem is growing fast, yet there is almost no way to confirm what a plugin does under the hood before you let it in. dsh-plugin-guard adds a purely static security checkpoint — it reads, scores, and locks; it never executes the target code.

The tool works on two surfaces. The Gate surface offers plugin_audit for a pre-install static sweep and plugin_verify for a post-install hash-and-capability lock. A 100-point baseline is deducted via P0 (−40), P1 (−12), and P2 (−3) findings; any P0 or a total below 40 triggers a hard block, while any P1 or a score below 75 raises a warning. The Clinic surface adds plugin_peers, which compares local fingerprint bundles and queries GitHub topic:dsh-plugin when local data is thin, and plugin_detox, which performs a mechanical amputation of dangerous segments rather than an equivalent rewrite.

It is deliberately scoped: no output redaction, no general-purpose SAST, and no claim that a passing plugin is safe. It simply turns audit before you install into a single command that can live in a CI pipeline. It is built for admins who self-host DeepSeek and need a uniform plugin-security baseline, and for individual users who keep profile bundles local and prefer not to ship plugin fingerprints to a remote service.