dependency-audit-wasp-drone — Claude Code subagent
dependency-audit-wasp-drone — a subagent for vulnerability scanning, CVE triage, SBOM generation and package signature verification. Use it to set up Renovate or Snyk, enforce lockfile discipline, or verify provenance before release.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install wasp-nest-core@wasp-nestWhat dependency-audit-wasp-drone does
Owns the full supply-chain security surface: scanner selection (Dependabot, Renovate, Snyk, socket.dev) based on platform and risk; CVE triage by CVSS, exploitability path and whether the flaw is transitive; SBOM generation (Syft + CycloneDX + Sigstore attestation); lockfile discipline via npm ci and minimumReleaseAge; provenance verification (npm Sigstore, PyPI PEP 740, Cargo signing).
Trigger on: "audit our dependencies", "set up Renovate", "generate SBOM", "npm audit is noisy", "lockfile hardening", "verify provenance", or any dependency update and vulnerability task. Works with npm, pnpm, pip, uv, poetry, cargo. Routes application vulnerabilities to security-wasp-drone, Docker scanning to devops-wasp-drone, and licensing disputes to legal.
Critical insight: npm audit is a CVE compliance tool, not a supply-chain control. When the axios maintainer account was hijacked in March 2026, a backdoor landed in 40 minutes with no CVE assigned—npm audit stayed green. socket.dev behavioral analysis and Renovate's minimumReleaseAge gate detect this class of attack.
What it helps with
- choose between Dependabot, Renovate and Snyk for your project setup
- triage critical CVEs and separate signal from noise in security advisories
- generate and sign SBOM for release artifacts and attach to tags
- enforce lockfile discipline and block unstable release versions
- verify npm signatures and package provenance before merge
Example prompts for the agent
- Audit our dependencies. We use npm, GitHub Actions, package-lock.json
- Set up Renovate with minimumReleaseAge and automerge for patches only
- Generate SBOM with Sigstore for our release, bind it to the tag
How to install dependency-audit-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install wasp-nest-core@wasp-nest2Manually: put the files in place
.claude/agents/dependency-audit-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/dependency-audit-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/dependency-audit-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about dependency-audit-wasp-drone
How do I install dependency-audit-wasp-drone in Claude Code?
Run /plugin marketplace add legioncodeinc/vibe-coding-tools, then /plugin install wasp-nest-core@wasp-nest. The agent will be available at .claude/agents/dependency-audit-wasp-drone.md.
What does dependency-audit-wasp-drone do?
Manages the full supply-chain surface: selects and configures scanners (Dependabot, Renovate, Snyk, socket.dev), triages CVEs, generates SBOM with attestation, enforces lockfile integrity, and verifies package signatures.
Why socket.dev if I already run npm audit?
npm audit catches known CVEs; socket.dev detects behavioral threats like maintainer account hijacks. Early release age and anomalous package behavior are signals npm audit cannot see.