vulnerability-scanner

Scan codebases for dependency vulnerabilities, hardcoded secrets, and dangerous patterns.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ntdev204/rai_ws --skill vulnerability-scanner-ntdev204
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vulnerability-scanner
Source: https://github.com/ntdev204/rai_ws/tree/main/.agent/skills/vulnerability-scanner
Command: npx skills add https://github.com/ntdev204/rai_ws --skill vulnerability-scanner-ntdev204

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps identify and mitigate security risks within a codebase by scanning for vulnerabilities, hardcoded secrets, and dangerous code patterns, aligning with modern security best practices.

Core Features & Use Cases

  • Dependency Analysis: Checks for known vulnerabilities in project dependencies (OWASP A03).
  • Secret Detection: Scans for hardcoded API keys, tokens, and credentials (OWASP A04).
  • Code Pattern Analysis: Identifies risky code constructs like injection vulnerabilities and insecure configurations (OWASP A05, A02).
  • Use Case: Before deploying a new feature, run this scanner to ensure no secrets are exposed and that the code adheres to secure coding standards, preventing potential breaches.

Quick Start

Use the vulnerability-scanner skill to perform a full 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 codebase for hardcoded secrets and vulnerable dependencies?

Scanning for hardcoded API keys and tokens involves analyzing project files using regex pattern matching to detect exposed credentials, aligning with OWASP A04 security best practices to prevent potential credential breaches before deployment.

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

The best way to check project dependencies for known vulnerabilities is performing dependency analysis using npm audit for supply chain security, which identifies known risks in your project packages and aligns with OWASP A03 standards.

Does this security scanner work with Python and JavaScript configuration files?

Yes, this security scanner works with Python and JavaScript configuration files, analyzing project files to detect dangerous code patterns like injection vulnerabilities and insecure configurations per OWASP A05 and A02 guidelines.

Can I identify insecure code patterns and injection vulnerabilities before deployment?

Yes, you can identify insecure code patterns and injection vulnerabilities before deployment by running a full security scan on your current project directory to ensure your code adheres to secure coding standards.

What types of OWASP security risks does a codebase vulnerability scanner detect?

A codebase vulnerability scanner detects OWASP risks including A03 for dependency vulnerabilities, A04 for hardcoded secrets, and A05 and A02 for dangerous code patterns like injection vulnerabilities and insecure configurations.