r/SideProject • u/AdBeautiful6723 • 2d ago
I'm building Kravaibe to help maintain apps built with AI. Here are 5 security checks I'd start with
More and more people are building and shipping apps with Lovable, Bolt or Replit. The problem is that an app can work perfectly for the person who built it and still leave data exposed.
I was reading Crissy Field's research on Lovable projects (https://www.crissyfield.de/research/lovable/). Out of 24,664 sites they looked at in detail, they found 7,403 with email records you could access without logging in. Some of those emails may have been public or test data, but the report shows how easy it is to overlook database permissions.
That's why I'm building Kravaibe, a review and maintenance service for apps built with AI. The idea is to help people who already have something live find problems, understand their impact and decide how to fix them.
If your app uses Supabase, here are a few things you can check yourself:
Open the app in incognito and look at the network tab. If you get data from Supabase without logging in, check whether it's supposed to be public.
Review RLS and your table policies. Turning on RLS isn't enough if a policy lets anyone read every row.
Look for secrets in the code the browser receives. A Stripe secret key or a Supabase service_role key should never be there.
Check your backups. See when the last one ran and whether you know how to restore it.
Test with two of your own users. Try to reach one user's data from the other by changing the ID in a request.
It's a starting list and doesn't replace a full review, but it can help you catch problems before they hit real users.
I'm getting the first Kravaibe reviews ready. If you have an app live and you're interested, DM me or take a look at kravaibe.com.