scan

Identifies security vulnerabilities across codebases using multi-tool SAST, dependency and configuration scans.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/onesmartguy/raptor-claude-plugins --skill scan-onesmartguy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scan
Source: https://github.com/onesmartguy/raptor-claude-plugins/tree/main/plugins/security/skills/scan
Command: npx skills add https://github.com/onesmartguy/raptor-claude-plugins --skill scan-onesmartguy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Running security scans across a codebase is complex, time-consuming, and prone to missing critical issues. This skill consolidates SAST, dependency vulnerability checks, and configuration security checks into a single, repeatable process, helping teams ship safer software faster.

Core Features & Use Cases

  • SAST analysis across JavaScript/TypeScript, Python, Ruby, Go, Java, and .NET to identify code-level security flaws.
  • Dependency vulnerability scanning for multilingual ecosystems to surface known CVEs in dependencies.
  • Configuration security checks to detect insecure defaults, exposed secrets, and risky configurations.
  • It can scan entire repositories or targeted paths, and supports focused scans via a --focus option.
  • OWASP/CWE mapping of findings to help prioritize remediation.

Quick Start

Use the security scan skill to analyze a project for vulnerabilities starting from the repository root.

Frequently Asked Questions about scan

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

FAQPage Schema
How do I run a SAST and dependency vulnerability scan across a multi-language codebase?

To run a security scan across a multi-language codebase, this skill orchestrates parallel SAST, dependency, and configuration checks. It automatically detects JavaScript, Python, Ruby, Go, Java, and .NET projects, normalizing all findings into a unified report.

What is the best way to identify security vulnerabilities and map them to OWASP Top 10?

Identifying security vulnerabilities and mapping them to OWASP Top 10 is done by running comprehensive SAST and dependency checks. This skill normalizes scan results into a unified schema, mapping each finding to CWE and OWASP categories for risk prioritization.

Can I scan a specific directory path instead of an entire repository for security flaws?

Yes, you can scan targeted paths instead of an entire repository. The skill supports focused scans by using a specific focus option or dedicated flags, allowing you to analyze specific directories for code-level flaws and exposed secrets.

Does the security scan check for risky configurations and known CVEs in dependencies?

Yes, the security scan checks for risky configurations and known CVEs in dependencies. It executes configuration security checks to detect insecure defaults and exposed secrets, while simultaneously scanning multilingual ecosystems for dependency vulnerabilities.

Why do I need a unified schema for codebase security scan results?

A unified schema for security scan results is needed to consolidate findings from multiple SAST and dependency tools. This standardization allows you to effectively prioritize remediation by mapping normalized data directly to CWE and OWASP risk categories.