security-scanner

Name: security-scanner
Availability: InStock
Author: Lordjiggy

Detect hardcoded secrets and security vulnerabilities in source code.

Updated Aug 27, 2026

Search Tags:#developer tools #OWASP #security #vulnerability #secrets #code audit #scanning

Ready to run

npx skills add https://github.com/Lordjiggy/claude-code-marketplace --skill security-scanner-lordjiggy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-scanner
Source: https://github.com/Lordjiggy/claude-code-marketplace/tree/main/skills/security/security-scanner
Command: npx skills add https://github.com/Lordjiggy/claude-code-marketplace --skill security-scanner-lordjiggy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifying security vulnerabilities like hardcoded secrets, SQL injection, XSS, and insecure dependencies manually is difficult and requires specialized expertise, leaving applications exposed to significant risks. This Skill automates comprehensive security analysis.

Core Features & Use Cases

Secret Detection: Scans for hardcoded API keys, passwords, and tokens.
Injection Vulnerability Detection: Identifies SQL injection, command injection, and XSS attack vectors.
Dependency Audit: Checks for insecure dependencies using tools like npm audit or pip-audit.
Use Case: Perform a quick security scan on a codebase to find critical vulnerabilities, audit dependencies for known security flaws, or get suggestions to fix common OWASP Top 10 issues before deployment.

Quick Start

Scan my code for security issues.

Frequently Asked Questions about security-scanner

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

FAQPage Schema

How do I scan code for hardcoded secrets and vulnerabilities?▼

Scanning code for secrets and vulnerabilities detects hardcoded API keys, passwords, SQL injection, XSS, and insecure dependencies. This Skill applies phase-based checks across secret detection, injection risks, and OWASP Top 10 controls, producing structured scan outputs with remediation guidance.

Can I use this to audit dependencies for security flaws?▼

Yes. Dependency audit checks for insecure packages using tools like npm audit and pip-audit, identifying known vulnerabilities before deployment and reducing exposure to compromised libraries.

What security vulnerabilities does code scanning detect?▼

Code scanning detects hardcoded secrets, SQL injection, command injection, XSS attack vectors, CORS misconfigurations, CSP policy gaps, and weak cryptographic implementations across source code during development and CI pipelines.

How do I integrate security scanning into my CI pipeline?▼

Security scanning integrates into CI pipelines using Bash workflows and file globbing to automatically locate secrets, injection risks, and dependency vulnerabilities during build stages, producing structured outputs for gates and notifications.

What's the difference between manual code review and automated scanning?▼

Automated scanning identifies hardcoded secrets and common OWASP Top 10 vulnerabilities at scale without specialist expertise, covering injection vectors and dependency flaws faster than manual review while reducing human oversight gaps.

Can scanning work across multiple codebases and languages?▼

Scanning uses language-agnostic techniques—Grep pattern matching, file globbing, and dependency checkers—to detect secrets and misconfigurations across mixed-language codebases, making it suitable for polyglot environments.