cve-scan

Detect known CVEs in project dependencies using native package manager audit tools.

161|21|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/softspark/ai-toolkit --skill cve-scan-softspark
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cve-scan
Source: https://github.com/softspark/ai-toolkit/tree/main/app/skills/cve-scan
Command: npx skills add https://github.com/softspark/ai-toolkit --skill cve-scan-softspark

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Many projects use multiple package managers, and manually tracking known security vulnerabilities across them is error‑prone and time‑consuming.

Core Features & Use Cases

  • Automatic ecosystem detection – identifies npm, pip, composer, cargo, go, bundler, and dart manifests in the repository.
  • Native audit execution – runs each manager’s built‑in audit command (e.g., npm audit, pip-audit) without installing third‑party scanners.
  • Unified severity‑sorted report – merges findings into a single view, highlights critical and high risks, and offers JSON output.
  • Fix mode – optionally runs the managers’ automatic fix commands when the --fix flag is supplied.
  • Graceful handling of missing tools – reports missing utilities and provides install hints instead of failing.

Use case example: a mixed‑language web service that includes a Node front‑end and a Python back‑end can be scanned in a single command to surface any vulnerable packages before deployment.

Quick Start

Run the cve-scan skill to audit all dependencies in the current project and receive a concise vulnerability report.

Frequently Asked Questions about cve-scan

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

FAQPage Schema
How do I scan multiple package managers for known vulnerabilities in one go?

To scan dependencies for vulnerabilities across multiple ecosystems, the skill automatically detects npm, pip, composer, cargo, go, bundler, and dart manifests, then runs native audit commands to produce a unified severity-sorted report.

Can I automatically fix vulnerable dependencies found during a CVE scan?

Yes, you can fix vulnerable dependencies by supplying the --fix flag, which instructs the skill to execute each package manager's built-in automatic fix commands to update affected packages.

What native audit tools do I need installed to detect CVEs in project dependencies?

To detect CVEs, you need native audit tools installed such as npm audit, pip-audit, composer audit, cargo audit, govulncheck, bundle-audit, and dart pub outdated for the skill to execute.

What happens if a required audit tool is missing when scanning dependencies for vulnerabilities?

When a required audit tool is missing during a vulnerability scan, the skill gracefully handles it by reporting the missing utility and providing install hints instead of failing the entire process.

Does this vulnerability scanner work with both Node and Python dependencies in the same repository?

Yes, the vulnerability scanner works with mixed-language repositories by detecting and auditing both Node and Python dependencies, merging findings into a single severity-sorted report with optional JSON output.

How does automatic ecosystem detection work for auditing project dependencies?

Automatic ecosystem detection works by identifying package manifests like package.json, requirements.txt, or Cargo.toml in the repository, allowing the skill to run the corresponding native audit commands without manual configuration.