Vibe Safe

Building VibeSafe has taught me something I didn't expect:

Finding security issues is only half the problem. Helping people understand what to do next is just as important.

Our first approach was simple — scan the code, find issues, and show the results.

But as the scanner became more powerful, the results became more complicated.

A developer could see:

🔴 Critical issues
🟠 High-risk issues
🟡 Medium issues
📁 File locations
💻 Code snippets
🛠️ Recommended fixes

Technically, that's useful.

But for someone who isn't a security expert, it can quickly become overwhelming.

So we're changing the experience.

Instead of simply saying:

"You have 8 security issues."

We want VibeSafe to answer three questions:

1. What is wrong?
2. Why does it matter?
3. How do I fix it?

And then make it easy to fix → rescan → verify.

That's becoming an important part of what VibeSafe is about.

AI makes it incredibly easy to build an app quickly.

But getting from "it works" to "it's safe to ship" is a different problem.

That's the problem I'm trying to solve.

I'd love feedback from other founders:

When a security tool gives you a long list of issues, what information do you actually want to see first?

I've been building VibeSafe because I kept seeing the same pattern with AI-built apps:

The app works.
The UI looks good.
The deployment succeeds.

But what's actually happening underneath?

Are secrets exposed?
Is authentication implemented correctly?
Are there insecure endpoints?
Are there runtime errors?
Does the deployed app actually behave the way the builder thinks it does?

That's what we're trying to solve with VibeSafe.

We're currently testing a workflow that can scan code/files/GitHub, test a live website, and run Launch Check against the actual application.

I'm still figuring out what the minimum useful security check for an AI-built app should be.

If you build with Cursor, Claude, ChatGPT, Lovable, Bolt, Replit, etc. — what's the security check you wish existed before you hit “deploy”?

Hey Indie Hackers 👋

I’m building VibeSafe, a security scanner for apps built with AI.

AI makes it incredibly easy to build and launch software, but it’s also easy to accidentally ship security issues you didn’t notice.

VibeSafe helps AI builders find potential security problems before they ship.

I’m also working on VibeSafe Builder, where the goal is to make AI-powered building faster and more practical.

The bigger vision is simple:

Build with AI → Scan → Fix → Ship safely.

We’re still early, and I’d love feedback from other indie hackers and people who are vibe coding.

What’s the biggest security problem you’ve encountered when building with AI?

I’d love to hear what you think. 🚀

Website: https://www.vibesafe.info/