sca-audit

Scan project manifests and lockfiles for known CVEs across multiple ecosystems.

141|14|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/OWASP/secure-agent-playbook --skill sca-audit-owasp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sca-audit
Source: https://github.com/OWASP/secure-agent-playbook/tree/main/skills/sca-audit
Command: npx skills add https://github.com/OWASP/secure-agent-playbook --skill sca-audit-owasp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the identification and triage of known CVEs across a project's dependencies, reducing risk and helping teams prioritize remediation.

Core Features & Use Cases

  • Dependency discovery: Locate all manifests and lockfiles across ecosystems to ensure comprehensive coverage.
  • Vulnerability scanning: Run appropriate scanners (OSV, npm audit, pip-audit, govulncheck, trivy) to collect CVE data.
  • Risk triage: Assess exploitability, exposure, and patch availability to produce actionable remediation steps.

Quick Start

Run a full dependency CVE scan against your project to surface vulnerabilities.

Frequently Asked Questions about sca-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan dependencies for CVEs across multiple ecosystems?

To scan dependencies for CVEs, apply this tool to manifests like package.json, requirements.txt, go.mod, pom.xml, Gemfile, and Cargo.toml to run appropriate scanners and collect vulnerability data.

What's the best way to triage open-source vulnerabilities before deployment?

The best way to triage open-source vulnerabilities is to scan lockfiles and manifests to assess exploitability, exposure, and patch availability, which produces actionable remediation steps for deployment.

Can I use npm audit and pip-audit to scan lockfiles for known vulnerabilities?

Yes, you can use npm audit and pip-audit to scan lockfiles. The tool specifies required scanners including osv-scanner, pip-audit, govulncheck, npm audit, and trivy to collect CVE data across ecosystems.

How does dependency vulnerability triage assess exploitability and fix availability?

Dependency vulnerability triage assesses exploitability and fix availability by running scanners on manifests and lockfiles to evaluate reachability, exposure, and patch status, producing actionable remediation steps.

Does dependency scanning work with both manifests and lockfiles?

Yes, dependency scanning works with both manifests and lockfiles. It locates files like package.json, requirements.txt, go.mod, pom.xml, Gemfile, Cargo.toml, and lockfiles to ensure comprehensive CVE coverage.

What scanners do I need to identify CVEs in project dependencies?

To identify CVEs in project dependencies, you need scanning tools such as osv-scanner, npm audit, pip-audit, govulncheck, and trivy, which the tool specifies to collect vulnerability data.