vulnerability-scanner

Run the security_scan.py script with the project path as an argument. It searches code and config files for patterns matching API keys, AWS credentials, database connection strings, private keys, and JWT tokens, then reports findings by severity.

The scanner checks four areas: dependency supply chain risks including missing lock files and npm audit results, hardcoded secrets, dangerous code patterns like eval and SQL string concatenation, and insecure configurations such as debug mode and wildcard CORS.

Use the --scan-type flag with one of the options: deps, secrets, patterns, or config. For example, running with --scan-type secrets scans only for hardcoded credentials and skips dependency and configuration checks.

Yes, it scans files with extensions including .js, .ts, .jsx, .tsx, .py, .go, .java, .rb, and .php, plus config files like .json, .yaml, and .env. It also runs npm audit automatically when a package.json is present.

Findings are classified as critical, high, medium, or low based on the pattern matched. The methodology combines CVSS base severity, EPSS exploit likelihood, asset value, and exposure to decide whether an issue needs immediate action or scheduled remediation.

Pattern-based scanning can produce false positives and cannot detect business logic flaws or complex authentication bypasses. The skill recommends combining automated scans with threat modeling, attack surface mapping, and manual review of high-risk code paths.