vulnerability-scanner

Scan project directories for supply chain vulnerabilities, hardcoded secrets, dangerous code patterns, and insecure configurations.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/namninhnd/PrelimStruct --skill vulnerability-scanner-namninhnd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vulnerability-scanner
Source: https://github.com/namninhnd/PrelimStruct/tree/main/.claude/skills/vulnerability-scanner
Command: npx skills add https://github.com/namninhnd/PrelimStruct --skill vulnerability-scanner-namninhnd

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps identify and prioritize security vulnerabilities within a codebase, reducing the risk of breaches and ensuring compliance with security best practices.

Core Features & Use Cases

  • Dependency Analysis: Scans project dependencies for known vulnerabilities (OWASP A03).
  • Secret Detection: Finds hardcoded secrets like API keys and passwords (OWASP A04).
  • Code Pattern Scanning: Identifies dangerous code patterns that could lead to injection or XSS (OWASP A05).
  • Configuration Review: Checks for common security misconfigurations (OWASP A02).
  • Use Case: Before deploying a new web application, run this Skill to proactively find and fix critical vulnerabilities in dependencies, secrets, and code patterns, preventing potential data breaches.

Quick Start

Run a comprehensive security scan on the current project directory.

Frequently Asked Questions about vulnerability-scanner

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

FAQPage Schema
How do I scan my project for hardcoded secrets and API keys?

To detect hardcoded secrets, you can scan your project directory for embedded API keys and passwords. This identifies sensitive data exposure risks aligned with OWASP A04, enabling you to proactively remove credentials before deployment.

What is the best way to check project dependencies for known vulnerabilities?

Checking project dependencies involves scanning them for known supply chain vulnerabilities, targeting OWASP A03 risks. It reviews package files to identify compromised libraries, helping you prioritize updates and reduce breach risks before deployment.

Can I check my codebase for dangerous code patterns and injection risks?

Yes, code pattern scanning identifies dangerous code patterns that could lead to injection or cross-site scripting attacks. This targets OWASP A05 risks by analyzing your source files for insecure coding practices.

Does this security scanner check for insecure configuration files?

Yes, configuration review checks for common security misconfigurations in your project files, addressing OWASP A02. It analyzes your setup to identify insecure settings, ensuring compliance with security best practices before deployment.

Can I run a targeted security scan for just dependencies or secrets?

Yes, you can run targeted security scans for dependencies, secrets, code patterns, or configuration files. This allows you to isolate and validate specific risk categories without running a full comprehensive project scan.