vulnerability-scanner

Scan projects for OWASP 2025 vulnerabilities, secrets, and supply chain risks.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/Helcio-Nogueira/Painel_Inteligente_Hackaton_2026 --skill vulnerability-scanner-helcio-nogueira
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vulnerability-scanner
Source: https://github.com/Helcio-Nogueira/Painel_Inteligente_Hackaton_2026/tree/main/.agents/skills/vulnerability-scanner
Command: npx skills add https://github.com/Helcio-Nogueira/Painel_Inteligente_Hackaton_2026 --skill vulnerability-scanner-helcio-nogueira

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Security reviews are often inconsistent, miss critical issues like hardcoded secrets or vulnerable dependencies, and fail to prioritize findings by real exploitability. This Skill provides a structured methodology and an automated scanner to detect, classify, and prioritize vulnerabilities across code, dependencies, and configuration. ## Core Features & Use Cases - Automated Security Scanning: Run scripts/security_scan.py to detect hardcoded secrets, dangerous code patterns (eval, SQL concatenation, unsafe deserialization), missing lock files, and insecure configurations, with JSON or summary output. - OWASP 2025 Alignment: Built-in guidance and checklists covering the OWASP Top 10:2025, including the new Supply Chain Security (A03) and Exceptional Conditions (A10) categories. - Risk Prioritization: Combines CVSS, EPSS, asset value, and exposure to classify findings as Critical, High, Medium, or Low with actionable remediation guidance. - Use Case: Before deploying a web application, run the scanner against the project directory to catch exposed API keys, npm dependency vulnerabilities, and missing security headers, then use the checklists to verify authentication and data protection controls. ## Quick Start Ask the AI to scan your project directory for security vulnerabilities and report any critical findings with remediation steps.

Frequently Asked Questions about vulnerability-scanner

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

FAQPage Schema
How do I scan a project for security vulnerabilities with Python?▼

Run python scripts/security_scan.py followed by the project path to execute a full scan covering dependencies, secrets, code patterns, and configuration. Use the --scan-type flag with deps, secrets, patterns, or config to run a targeted scan, and --output summary for a human-readable report.

What types of secrets can a security scanner detect in code?▼

The scanner detects API keys, bearer tokens, AWS access keys, Azure and GCP credentials, database connection strings, private keys, SSH keys, JWT tokens, and hardcoded passwords. Each finding is classified by severity from medium to critical.

What changed in OWASP Top 10 2025 compared to 2021?▼

OWASP 2025 merged SSRF into Broken Access Control (A01), elevated Security Misconfiguration (A02), added Software Supply Chain Failures (A03), and introduced Mishandling of Exceptional Conditions (A10). The focus shifted from symptoms to root causes.

Does the security scanner work with JavaScript and Python projects?▼

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

How should vulnerability findings be prioritized for remediation?▼

Prioritize by combining CVSS severity, EPSS exploit likelihood, asset value, and exposure. Actively exploited vulnerabilities (EPSS above 0.5) require immediate action, CVSS 9.0 or higher is high priority, and lower scores can be scheduled based on business context.

What are the limitations of automated pattern-based security scanning?▼

Pattern-based scanning can produce false positives and cannot detect business logic flaws, insecure design issues, or complex authentication bypasses. It should be combined with threat modeling, manual code review, and the provided checklists for complete coverage.