How does VibeScan ensure code privacy?

VibeScan prioritizes your code's privacy by performing all scanning operations locally on your machine. This means your code never leaves your development environment, ensuring maximum security.

VibeScan is a security scanning tool designed for developers, which identifies leaked secrets, dangerous code patterns, and Git hygiene issues directly within your development environment.

How do I integrate VibeScan into my development workflow?

You can easily install VibeScan using pip. It's designed for seamless integration with AI development environments like Claude Code, allowing you to initiate scans with simple prompts once configured.

What types of security issues can VibeScan detect?

VibeScan is comprehensive, detecting 14 categories of leaked secrets (like cloud credentials, API keys), dangerous code patterns such as `eval()`, `exec()`, and SQL injection, and Git hygiene problems like missing `.gitignore` files or unignored sensitive data.

VibeScan

Name: VibeScan
Author: Aguantar

byAguantar

0•

Developer Tools

Security & Testing

Scans projects for leaked secrets, dangerous patterns, and security vulnerabilities directly within your development environment.

VibeScan is a security scanning tool designed to help developers identify and mitigate potential risks within their projects. Operating as an MCP server, it integrates seamlessly to scan for a wide array of security issues, including 14 categories of leaked secrets (e.g., cloud credentials, API keys, environment variables), dangerous code patterns like SQL injection or `eval()`, and poor Git hygiene. All analysis is performed locally, ensuring that sensitive code never leaves the user's machine, providing a secure and efficient way to enhance code security.

Key Features

01Identifies dangerous code patterns such as `eval()`, `exec()`, and SQL injection

02Performs all scanning locally to ensure code privacy and security

03Scan projects for secrets, dangerous patterns, and Git hygiene issues

04Detects 14 categories of leaked secrets across various file types

05Checks for Git hygiene issues like missing `.gitignore` and unignored sensitive files

060 GitHub stars

Use Cases

01Automatically scan projects for leaked secrets during development

02Identify dangerous code patterns and potential security vulnerabilities in a codebase

03Ensure proper Git hygiene to prevent accidental exposure of sensitive files