Security Scanning

Scan codebases for vulnerabilities, secrets, and security anti-patterns.

7|1|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/eyadsibai/ltk --skill security-scanning-eyadsibai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Security Scanning
Source: https://github.com/eyadsibai/ltk/tree/main/plugins/ltk-devops/skills/security-scanning
Command: npx skills add https://github.com/eyadsibai/ltk --skill security-scanning-eyadsibai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need to identify and mitigate security risks within codebases, protecting against data breaches, unauthorized access, and system compromise.

Core Features & Use Cases

  • Secrets Detection: Finds accidentally committed API keys, private keys, passwords, and other sensitive credentials.
  • Vulnerability Identification: Detects common web vulnerabilities like SQL Injection, XSS, Command Injection, and Path Traversal.
  • Dependency Auditing: Checks project dependencies for known vulnerabilities (CVEs).
  • Use Case: Before deploying new code, run a full security scan to ensure no hardcoded secrets were introduced and that the code adheres to secure coding practices, preventing potential exploits.

Quick Start

Scan the current project for any security vulnerabilities and sensitive information.

Frequently Asked Questions about Security Scanning

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

FAQPage Schema
How do I scan code for hardcoded secrets and API keys before deployment?

To scan code for hardcoded secrets, the Skill uses pattern matching with tools like grep to identify accidentally committed API keys, private keys, passwords, and other sensitive credentials across your codebase.

Can I detect OWASP Top 10 vulnerabilities like SQL Injection and XSS in my project?

Yes, you can detect OWASP Top 10 vulnerabilities including SQL Injection, XSS, Command Injection, and Path Traversal through comprehensive security anti-pattern analysis of your codebase.

How do I audit project dependencies for known CVEs across various languages?

You can audit project dependencies for known CVEs using dependency auditing tools like pip-audit and safety to check installed packages against vulnerability databases.

Does this security scanning require specific tools or environments to work?

Security scanning requires specific pattern matching and auditing tools like grep, pip-audit, and safety to identify vulnerabilities, secrets, and report security risks with severity levels.

What is the best way to run a full security scan on a codebase?

The best way to run a full security scan is to analyze the entire codebase comprehensively, detecting vulnerabilities, secrets, and security anti-patterns while auditing dependencies for known risks.

Why does dependency auditing report security risks with severity levels?

Dependency auditing reports security risks with severity levels to help prioritize remediation efforts, distinguishing between hardcoded credentials, OWASP vulnerabilities, and CVEs found in project dependencies.