security-scanner

Scan codebases for OWASP Top 10 issues, CVEs, and hardcoded secrets.

Updated Dec 4, 2025
One-click install
npx skills add https://github.com/christianearle01/claude-config-template --skill security-scanner-christianearle01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-scanner
Source: https://github.com/christianearle01/claude-config-template/tree/main/.claude/skills/security-scanner
Command: npx skills add https://github.com/christianearle01/claude-config-template --skill security-scanner-christianearle01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates comprehensive security validation for codebases to identify OWASP Top 10 issues, CVEs in dependencies, and hardcoded secrets, delivering confidence-scored reports.

Core Features & Use Cases

  • OWASP Top 10 Scan: automated detection of common vulnerabilities in code and configurations.
  • Dependency CVE Scan: identify vulnerable or outdated dependencies across package managers.
  • Secrets Detection: locate hardcoded credentials, API keys, and tokens in the repository.
  • Full Security Audit: end-to-end security assessment combining code, dependencies, and configuration.
  • Use Case: Before release, run a full security audit to surface critical issues and generate a remediation plan.

Quick Start

Run the quickstart script to perform an initial security assessment:

  • Command: ./scripts/quickstart.sh
  • Optional: Provide a path to target project and enable verbose output.

Frequently Asked Questions about security-scanner

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

FAQPage Schema
How do I automate security checks for OWASP Top 10 vulnerabilities in my codebase?

You can automate a full security audit to check for OWASP Top 10 issues, dependency CVEs, and hardcoded secrets by running the quickstart script, which generates confidence-scored reports and actionable remediation plans.

What is the best way to scan dependencies for CVEs before a release?

Scanning dependencies for CVEs across package managers identifies vulnerable or outdated libraries before release, providing confidence-scored reporting to prioritize updates and improve your overall security posture.

How do I detect hardcoded secrets and API keys in my repository?

Detecting hardcoded secrets and API keys requires scanning the repository to locate exposed credentials and tokens, applying pattern-based detection to accurately identify sensitive data and generate remediation guidance.

Can I run a full security audit locally during development?

Yes, you can run a full security audit locally during development or code reviews by executing the quickstart script, which performs end-to-end assessments combining code, dependencies, and configuration validation.

Does this automated security scanner require any external dependencies?

This automated security scanner operates without external dependencies, applying pattern-based detection directly to your codebase to identify OWASP issues, dependency CVEs, and hardcoded secrets during code reviews.