Free health check for Lovable, Bolt, v0 & Replit apps

We look at your app the way a stranger would β€” and tell you, in plain words, what they can see that they shouldn't. Secret keys sitting in public code, open customer data, missing Google basics. Fixed in minutes, not days.

Made for apps built with
πŸ’œ Lovable ⚑ Bolt β–² v0 πŸŒ€ Replit πŸ–±οΈ Cursor

Free Β· About 10 seconds Β· No sign-up

πŸ’¬

This happens every week

Real-style posts from builders on X, sharing safety problems they found in their own apps. Different apps, same lesson: something public that should never have been public.

πŸ§‘β€πŸ’»
indie builder@buildsinpublic Β· 2d

found out my API key was sitting in my app's page source in plain sight, and strangers had been using it without me knowing. I didn't even know you could VIEW the code like that 😭 check your keys people

πŸ‘©β€πŸš€
shipping my first app@firsttimedev Β· 4d

a kind stranger just emailed me a spreadsheet of MY OWN USERS. my Supabase table was wide open, no row level security. anyone with the link could read every email address. fixed now but wow

πŸ§”
lovable fan@vibecoder Β· 1w

TIL the "admin" page of my app was only hidden in the menu. the page itself had zero protection. a user guessed /admin and could see everything. hiding a button is not security πŸ’€

πŸ‘±β€β™€οΈ
micro-saas diary@microsaasdiary Β· 1w

three weeks after launch I found out Google had never indexed my site. no sitemap, and my robots file was blocking everything from the starter template. three weeks of invisible. check the basics!!

😬

One small gap is all it takes

Most AI-built apps have a gap or two hiding in plain sight. Here's why they're worth fixing:

πŸ’Έ

Charges that aren't yours

If your OpenAI key is sitting in public code, anyone can use it β€” and the usage lands on your account, not theirs. Builders tend to find out about this one the hard way.

πŸ“‚

Customer data out in the open

An open database table means visitors can read your users' emails and details β€” information your users trusted you to keep private.

🚫

Your app gets pulled

Platforms and providers shut down apps with keys visible in public code or customer data left open. Sometimes with no warning and no appeal.

πŸ’”

Trust is gone

Users forgive bugs. They don't forgive finding their email address in a stranger's spreadsheet. Reputation doesn't have an undo button.

πŸ‘€

What a stranger can see

No special skills needed. No special tools. Just a browser β€” the same one you're using now.

1

A stranger opens your app

They find it on X, Product Hunt, or Google. It looks lovely. They're curious how it works.

2

They open the code view

Two clicks in any browser: "View source". Everything your app sends to visitors is right there β€” including things you never meant to send.

3

They find a secret key

Sitting in plain sight, exactly like this:

// your app's code, visible to anyone
const openai = "sk-β€’β€’β€’β€’β€’β€’β€’β€’β€’β€’";
const db = "supabase.co/…";
4

Your key gets used

A key in plain sight can end up used on other people's projects β€” and the usage shows up on your account. Much better to spot it in a scan first.

πŸͺ„

How it works

Step 1 πŸ”—

Paste your link

Drop in your app's address. No sign-up, no login, nothing to install.

Step 2 🩺

We check it

We run the same 8 checks a careful human would β€” in about 10 seconds β€” and explain every problem in plain words.

Step 3 πŸ“‹

Copy the fix

Every problem comes with a ready-made prompt. Paste it into Lovable, Bolt or Cursor, and the builder fixes it for you.

🩺

Your launch checklist

The 8 things we check on every scan β€” the same checks, every time, for every app.

πŸ” Safety

πŸ”‘

Secret keys

Are your private keys (OpenAI, Stripe, database) hidden β€” or sitting in your app's public code where anyone can copy them?

If this fails: anyone can use your keys, and the usage lands on your account. This is the most common safety gap in AI-built apps.
πŸ”’

Safe connection (HTTPS)

Does your app use a locked, encrypted connection β€” the padlock in the browser β€” so logins and payments can't be snooped on?

If this fails: visitors see a scary "Not secure" warning and anything they type can be read by others on the same network.
πŸ›‘οΈ

Browser safety settings

Does your app send the standard safety headers that tell browsers to block common tricks β€” injected scripts, sneaky iframes, fake content types?

If this fails: your app is missing the cheap, built-in protections browsers offer for free. One small config change fixes it.
πŸͺž

No fake copies (clickjacking)

Can another site secretly wrap your app inside their own page and trick your users into clicking things they can't see?

If this fails: a copycat page can put invisible buttons over your real ones and trick your users into clicks they never meant to make.

πŸ—„οΈ Customer data

πŸ—ƒοΈ

Open database tables

If you use Supabase or a similar database: can a stranger read tables like profiles or users without logging in β€” or did you switch on Row Level Security?

If this fails: your customers' emails and details can be downloaded by anyone. This is the gap builders most regret missing.

πŸ”Ž Google

🏷️

Title and description

Does your app have a real page title and description β€” or is it still the starter template's "Vite + React" that Google shows to the world?

If this fails: Google shows a blank or template title for your app, and people scroll right past it.
πŸ—ΊοΈ

Site map and robots file

Does your site tell Google which pages exist (a sitemap) β€” and is your robots file accidentally telling Google to stay away?

If this fails: your app is effectively hidden from Google. People can only find it if they already have the link.
🧭

Broken links

Do the links and buttons on your public pages actually go somewhere β€” or do some land on error pages?

If this fails: visitors hit dead ends, lose trust, and Google quietly ranks you lower.
✨

Every problem comes with its fix

You never get a scary report and a shrug. Each problem includes a prompt written for your AI builder β€” copy, paste, done.

πŸ—ƒοΈ Problem: your "profiles" table can be read by anyone

High risk

Your customer list is sitting in an open database table. Here's the exact fix β€” give it to the same AI that built your app:

πŸ“‹ Paste this into Lovable, Bolt or Cursor
Turn on Row Level Security (RLS) for the "profiles" table in Supabase. Add a policy so each signed-in user can only read and update their own row (where user_id equals the logged-in user's id). Nobody who isn't logged in should be able to read the table at all. Show me the SQL and confirm when it's applied.
πŸͺ„ Pasted into Lovable β†’  Done in ~40 seconds βœ… Fixed on re-scan
πŸ“ˆ

What "fixed" looks like

The same app, before and after pasting three fixes into its builder. Try both reports yourself:

BEFORE
42/100
Not ready yet
  • Customer emails are open
  • OpenAI key is public
  • Hidden from Google
➜
AFTER Β· ~15 MINUTES OF FIXES
96/100
Ready to launch
  • Database locked to each user
  • Keys moved somewhere safe
  • Google can find every page
πŸ’°

Three ways to find the same problems

πŸ§‘β€πŸ’Ό

A pro security review

$500+

Great work, real expertise β€” and a waitlist, a big invoice, and a report full of jargon you'll have to decode yourself.

πŸ§‘β€πŸ’»

Doing it yourself

6+ hours

Blog posts, docs and forum threads β€” assuming you already know what to search for. Most builders don't know what they don't know.

πŸ’œ

VibeCheck

10 seconds

The same 8 launch checks, in plain words, with fixes you paste into your builder. Your first scan is free.

πŸ”

"Is my idea safe with you?"

Fair question. No β€” and here's exactly why we couldn't if we wanted to:

πŸ‘€

We only see what's public

We look at your app exactly the way any visitor β€” or Google β€” already can. If a stranger can see it, we can. If they can't, neither can we.

πŸšͺ

No code, no login

We never ask for your password, your builder account, or your source code. Your idea, your users' private data, your backend β€” all out of reach.

πŸ”

We only look, never change

A scan is read-only. We don't touch settings, click buttons inside your app, or change a single thing. The fixes are yours to paste β€” or ignore.

πŸ—‘οΈ

We don't keep your data

Your report lives at its link. We don't build a database of everyone's weak spots β€” that would be a strange thing for a security tool to do.

πŸ”—

Your report is just a link

Share it with a co-founder or keep it to yourself. No account, no dashboard full of your business details.

βš–οΈ

Same checks, every time

Every app gets the same 8 checks, scored the same way. No favourites, no scare tactics to make you pay β€” the free list shows every problem we find.

πŸ’œ

Simple, one-time pricing

No subscription. No "cancel before they charge you" games. Pay once, keep your report forever.

Problems list

$0
free Β· just add your email
  • All 8 checks, run in full
  • Every problem, in plain words
  • Risk level for each problem
  • Your score out of 100
Run a free scan
⭐ Most people pick this

Fix report

$9
one-time Β· not a subscription
  • Everything in the free list
  • A fix prompt for every problem
  • Prompts written for Lovable, Bolt & Cursor
  • Copy, paste, fixed β€” no jargon
  • Keep the report link forever
Get the fix report β€” $9

10 fix reports

$29
one-time Β· $2.90 per report
  • Everything in the fix report
  • 10 reports β€” for 10 apps, or re-scans
  • Credits never run out
  • Perfect if you ship often
Get 10 reports β€” $29

πŸ’³ Checkout is a secure Square payment page (sold by Future Assisting Co) that accepts card and Cash App Pay. Prefer to pay by Cash App directly? You can send it to $littlewm at checkout instead β€” those payments are verified by hand, and your report unlocks on the next daily check.

πŸ™‹

Questions, answered straight

Is my idea safe?
No. We only look at what's already public β€” the same things any visitor or Google can see. We never see your source code, your login, or anything behind a password. Your idea stays yours.
What is free?
The scan and the full problems list. All 8 checks run in full, and you see every problem we find, what it means in plain words, and how risky it is. Just add your email so we can send you the report link.
What do I get for $9?
The fix report: everything in the free list, plus a ready-to-paste fix prompt for every single problem. The prompts are written for AI builders like Lovable, Bolt and Cursor β€” paste one in, and the builder applies the fix. You keep the report link forever.
Is it a subscription?
No. You pay once. There is nothing to cancel, no renewal, and no surprise charge next month.
Can I pay with Cash App?
Yes β€” two ways. Square checkout accepts Cash App Pay alongside cards, so you can pay with Cash App right there. Or, at checkout, pick the Cash App tab and send the amount for your plan ($9 for one fix report, $29 for the 10-report pack) directly to $littlewm, putting your scan email in the payment note so we can match it to your report. Direct Cash App payments are verified manually β€” there is no automatic confirmation β€” so your report unlocks on the next daily check once we've confirmed the payment arrived.
How do the 10 reports work?
You get 10 fix-report credits for $29 β€” $2.90 each instead of $9. Use them on different apps or on re-scans of the same app after you've fixed things. Credits never run out or expire.
Is it safe?
Yes. A scan is read-only: we load your public pages and already-public code files, the same way a browser does. We don't log in, we don't submit forms, and we never change anything in your app.
What do you look at?
Your app's public pages and the code files your app openly sends to every visitor, your safety headers, whether your database tables answer strangers, and your Google basics β€” title, description, sitemap, robots file and links.
Do you keep my results?
Your report lives at its own link so you can come back to it. We don't sell results, share them, or keep a list of who failed what.
Do you check my code?
Only the code your app already shows the whole world β€” the files every visitor's browser downloads. We never see your private source code or your builder project. If you prefer, you can also paste code into the "Check pasted code" tab and scan it yourself, right here in your browser.
Does a high score mean my app is completely safe?
No β€” and anyone who promises that is not being straight with you. A high score means the 8 most common launch-day problems are handled: no keys visible in public code, no open tables, solid basics. It can't see inside your private systems, and no checklist covers everything. Think of it as locking your doors, not building a fortress.
My Supabase rules pass every review β€” can my tables still leak?
Yes β€” a policy can pass every review and still leak. A common AI-written policy is using (auth.uid() is not null): it checks that someone is logged in, not that the row is theirs. Any signed-in stranger can then pull everyone's rows β€” emails, stripe_customer_id and all β€” with one line in the browser console, and reviews miss it because the policy mentions auth.uid() and never uses (true). Fix it by testing with a second account (or a signed-out browser) and requiring user_id = auth.uid() on each row, then run VibeCheck's free scan to confirm nothing is readable without the right login.
πŸ“§

The 3 emails after your scan

After a scan, three short emails land in your inbox: your report, a nudge about your most urgent problem, and a follow-up on day three. Here they are in full, so there are no surprises:

πŸ›‘οΈ

A safety checker for your own app

VibeCheck is a defensive tool: it checks an app you own for safety gaps, using only what any visitor can already see. Three things worth knowing before you scan:

πŸ›‘οΈ

Made to protect, not to pry

It's built to check apps you own and hand you the fixes in plain words, so you can close the gaps yourself. It only ever looks at what's already public.

πŸ’»

Runs in your browser

Code you paste is scanned right here on your device β€” nothing is uploaded. Your report and settings stay in this browser too.

🏷️

Clear, one-time pricing

The scan and the full problems list are free. The fix report is $9 once, or $29 for ten reports β€” no subscription, nothing recurring.

πŸš€

Check your app before a stranger does

Ten seconds, plain words, fixes included. The stranger won't send you a friendly report first.

Check my app β€” free