quality-security-scan

Scan code for security vulnerabilities and unsafe patterns. Use before committing sensitive code or in security reviews.

⭐8stars🔀4forks📁View on GitHub🕐Updated Jan 3, 2026

When & Why to Use This Skill

The Security Scan skill is a comprehensive automated tool designed to identify security vulnerabilities, detect hardcoded secrets, and flag unsafe coding patterns within your codebase. It enhances software supply chain security by integrating secret detection, dependency auditing, and static analysis, ensuring that sensitive data and vulnerable code are identified before they reach production.

Use Cases

  • Pre-commit Secret Detection: Automatically scan code for API keys, AWS credentials, and private tokens to prevent accidental exposure in version control systems.
  • Dependency Vulnerability Auditing: Utilize tools like pip-audit to identify and remediate known security flaws in third-party libraries and packages.
  • Automated Security Code Review: Detect unsafe programming patterns such as SQL injection vectors, path traversal risks, and unvalidated input handling.
  • Pre-release Security Audits: Conduct a final security sweep of the codebase to ensure compliance with security best practices and OWASP standards before deployment.
namequality-security-scan
descriptionScan code for security vulnerabilities and unsafe patterns. Use before committing sensitive code or in security reviews.
mcp_fallbacknone
categoryquality
agenttest-engineer
user-invocablefalse

Security Scan Skill

Scan code for security vulnerabilities and unsafe patterns.

When to Use

  • Before committing code with secrets
  • Security review process
  • Handling sensitive data
  • Pre-release security audit

Quick Reference

# Check for committed secrets
./scripts/scan_for_secrets.sh

# Check Python dependencies
pip-audit

# Check unsafe patterns
./scripts/check_unsafe_patterns.sh

Security Checks

1. Secrets Detection

./scripts/scan_for_secrets.sh

Detects:

  • API keys and tokens
  • Passwords and credentials
  • Private keys (.key, .pem)
  • AWS credentials
  • Database credentials

2. Dependency Vulnerabilities

pip-audit              # Python packages
safety check          # Alternative scanner

3. Unsafe Code Patterns

./scripts/check_unsafe_patterns.sh

Looks for:

  • Hardcoded credentials
  • SQL injection vectors
  • Unsafe file operations
  • Unvalidated input

Prevention

.gitignore

Ensure sensitive files ignored:

.env
.env.local
*.key
*.pem
credentials.json
secrets/
aws/
google/
api-keys.txt

Pre-commit Hook

- id: detect-private-key
  name: Detect Private Key
- id: detect-aws-credentials
  name: Detect AWS Credentials

Common Vulnerabilities

Hardcoded Secrets

# ❌ Wrong
API_KEY = "sk_live_1234567890"
PASSWORD = "admin123"

# ✅ Correct
import os
API_KEY = os.getenv("API_KEY")
PASSWORD = os.getenv("DB_PASSWORD")

Unsafe File Operations

# ❌ Potential path traversal
fn load_file(path: String):
    var data = open(path).read()
    return data

# ✅ Validate path
fn load_file(path: String) -> String:
    if not is_safe_path(path):
        return error("Invalid path")
    return open(path).read()

SQL Injection

# ❌ Unsafe - string concatenation
query = "SELECT * FROM users WHERE id = " + user_id

# ✅ Safe - parameterized query
cursor.execute("SELECT * FROM users WHERE id = ?", (user_id,))

Workflow

# 1. Before committing
./scripts/scan_for_secrets.sh

# 2. Check dependencies
pip-audit

# 3. Check unsafe patterns
./scripts/check_unsafe_patterns.sh

# 4. If no issues, commit
git add .
git commit -m "feat: new feature"

# 5. If issues found, fix before committing
# ... move secrets to .env ...
# ... update dependencies ...
# ... fix unsafe patterns ...

Error Handling

Issue Fix
"Secret detected" Move to .env, add to .gitignore
"Unsafe dependency" Update to patched version
"Unsafe pattern" Refactor code to use safe approach

Best Practices

  1. Never commit secrets - Use environment variables
  2. Keep dependencies updated - Run pip-audit regularly
  3. Validate input - Always validate user input
  4. Use safe libraries - Prefer parameterized queries, etc.
  5. Review PRs - Include security review in PR process

Scripts Available

  • scripts/scan_for_secrets.sh - Detect committed secrets
  • scripts/check_unsafe_patterns.sh - Check code patterns
  • pip-audit - Check Python vulnerabilities
  • safety check - Alternative vulnerability scanner

References