security-scan

Scan codebases for security vulnerabilities in authentication, API endpoints, dependencies, and secrets.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of scanning a codebase for potential security vulnerabilities, saving time and reducing the risk of security breaches.

Core Features & Use Cases

  • Security Auditing: Scans code for common vulnerabilities and provides a report.
  • Scope Arguments: Customize the scan by focusing on specific areas such as authentication, API endpoints, dependencies, or secrets.
  • Use Case: Use this Skill to ensure that no sensitive information is leaking from your codebase and that your dependencies are secure.

Quick Start

Run a full security scan on your codebase by invoking the skill without any scope argument.

Frequently Asked Questions about security-scan

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

FAQPage Schema
How do I automate a codebase security audit for vulnerabilities?

Automate a codebase security audit by running a scan across your codebase to detect vulnerabilities in authentication, API endpoints, dependencies, and secrets using grep, git commands, and custom logic.

How can I detect hardcoded secrets and sensitive information in my source code?

Detect hardcoded secrets by scanning your codebase environment variables and source files. The security scan targets sensitive information leakage automatically, utilizing pattern matching to identify and report exposed credentials.

What is the best way to check dependencies for known security vulnerabilities?

Check dependencies for vulnerabilities by executing a targeted security scan with a dependency checking scope argument. This focuses the audit on your project's libraries to ensure no insecure dependency versions are present.

Can I scan only the authentication logic and API endpoints in my codebase?

Yes, you can scan only authentication logic and API endpoints by passing specific scope arguments to the security scan. This customizes the audit to focus precisely on those targeted risk areas instead of the full codebase.

Do I need to provide environment access for a codebase vulnerability scan?

Yes, you need to provide access to the codebase and environment variables for the vulnerability scan. This access allows the tool to utilize git commands and grep effectively to identify potential security risks accurately.

What limitations exist when using grep and git for codebase security auditing?

Limitations of using grep and git for security auditing include relying on pattern matching rather than semantic code execution, meaning it identifies potential textual risks but does not run dynamic runtime vulnerability tests.