AI Agent Hub
Back to plugins
🧩

dsh-vulnsec-bridge

admin-security Updated 2026.08.19

Run the following command in DeepSeek Harness:

dsh plugin install MariNanari/dsh-vulnsec-bridge

Paste the following prompt into your AI chat to install this plugin:

After cloning from https://github.com/MariNanari/dsh-vulnsec-bridge, run dsh plugin install MariNanari/dsh-vulnsec-bridge in the DeepSeek Harness terminal to install the plugin.

About this plugin

If you have been juggling VulnClaw for offensive tests and DeepSec Shield for code audits, you probably already know the friction: two CLIs, two virtualenvs, two sets of configuration conventions, and no unified entry point inside DSH to orchestrate them. dsh-vulnsec-bridge solves exactly that. It wraps both security CLIs into 18 DSH-callable tools and layers a graphical Security Workbench on top, so reconnaissance, vulnerability scanning, three-tier code audit, scope management, and one-click full-pipeline runs all happen in a single panel.\n\nThe workbench is reachable from the Settings tab or as a full-screen panel from the sidebar. Every control carries a hover tooltip, and results stream into the log area at the bottom with automatic redaction and a 120 KB truncation cap. Setting up the CLIs takes one click on the status bar: the installer creates an isolated venv, pulls source, runs pip, and verifies, all idempotent. DeepSec Spear enforces a scope-whitelist gate, and every offensive tool description explicitly states authorized targets only, so the safety boundary is baked into the tool layer rather than left to discipline.\n\nIt is well suited for security engineers who run regular code audits and supply-chain checks, CTF players and authorized-pentest practitioners who need the full recon-to-exploit pipeline, and teams that want to fold multiple security CLIs into one DSH-orchestrated workflow. The plugin has zero third-party runtime dependencies, the bridge layer calls only DSH official subprocess services, and it adopts a defensive-adaptation strategy so DSH upgrades degrade gracefully instead of crashing. Removal is clean: it never modifies any DSH official files.

Use Cases

  • Three-tier code audit and supply-chain check on target projects
  • Authorized full-pipeline pentesting: recon, scan, exploit in one flow
  • Centralized management of multiple security CLIs via a graphical workbench

Best For

  • Security engineers running regular code audits and supply-chain checks
  • CTF players and authorized-pentest practitioners needing the full attack chain
  • DevSec teams consolidating multiple security CLIs into one workflow