vulnerability-scanner

To scan a codebase for security vulnerabilities automatically, run the script against your project path to generate a JSON findings report. It checks dependencies, secrets, dangerous code patterns, and misconfigurations.

Yes, you can detect exposed secrets and API keys in source files. The scanner analyzes source and configuration files to identify credentials, cloud secrets, and API keys to prevent accidental exposure.

You can check project dependencies for OWASP vulnerabilities using the built-in dependency checks. It aligns with OWASP A03 to surface known vulnerable packages and identify missing lock files in your software project.

The best way to integrate vulnerability scanning into a CI pipeline is to run the scanner script to fail builds on critical findings. It automatically validates configurations and generates reproducible security reports for audits.

A vulnerability scanner catches insecure configurations and dangerous code patterns by flagging risky settings like CORS issues and debugging exposure. It also detects eval usage and unsafe deserialization in the codebase.

Yes, automated security scanning works without external dependencies. The Skill operates self-contained using its internal scripts and reference materials to analyze your repository and output findings.