CodeVibes - Because your AI code shouldn't vibe check itself into production
Hey Vibe coders,
Remember that feeling when you paste AI code, it works first try, and you're like "I'm literally unstoppable"?
Yeah, I had that. Then I actually read what I deployed.
Hardcoded API keys just vibing in my frontend. SQL queries that are basically open invitations for attackers. Auth middleware that sometimes forgets to auth. The vibes were NOT immaculate.
So I built CodeVibes - a free AI code auditor that roasts your code before production does.
What it does:
Analyzes your codebase with DeepSeek v3.2 and actually explains WHY things are broken
Scans security files first so you see the scary stuff immediately
Shows issues in real-time as it finds them
Gives your code a Vibe Score (0-100) based on how cooked it is
Works with GitHub OAuth, public and private repos
Your code never leaves the session
Why this exists:
We're all using AI to ship faster. But AI code has 1.7x more bugs than human code. We're basically speedrunning to incidents and calling it productivity.
Professional review tools cost $15-50/month. That's rent money for some of us. Security shouldn't be paywalled.
What makes it different:
Not just linting. It catches the stuff that makes you wake up to 47 Slack messages. Exposed secrets, injection vulns, broken auth, sketchy API calls.
The vibe:
Already scanned 50+ repos. Found critical issues in 68% of AI-assisted code. Average scan takes 45 seconds.
Still rough. Working on auto-fixes, Claude integration, and making the prompts even better.
Try it: codevibes.akadanish.dev
GitHub: github.com/danish296/codevibes
3 free scans to start. Connect GitHub for unlimited.
The move isn't "stop using AI." It's "use AI but actually check your work."
Built this because I needed it. Open sourcing it because I think we all do.
Feedback, contributions, and friendly roasts all welcome. Let's make AI-assisted coding less chaotic together.
What security stuff do you wish tools caught before you deployed? Genuinely curious what would make this more useful for how you actually code.
Replies