Vibe-Coded App Audit: Lovable Code, Supabase Security
Your app has real users, and you did not write the code or nobody on your team can read it. I audit it and tell you in writing which parts to keep, which to fix and which to rewrite, so you know what you have before you spend more on it.
The problem this solves
People are signing up and the app holds their data, but you cannot tell whether it is safe or what it would take to make it safe. A quote from a developer does not settle it, because the person quoting also gets paid for the work.
Deliverables
- A written verdict for each part of the app: keep, fix or rewrite, and why
- A list of what is dangerous right now, most urgent first
- The order to fix things in, so you can brief any developer
- On a Supabase or Firebase app: the results of my security checks on your real project
- A 30-minute call to go through it together
How does the audit work?
You can start for free. Run the Supabase security scan and the two-user tenant isolation test on your project and send me the results if you want to.
For the audit itself you give me read-only access to the code, the database and the hosting. I read the code, run the app and test who can reach which data with real accounts. Within 3 working days you get the written verdict, then we go through it on a 30-minute call.
Please do not email passwords or keys: I will explain how to set up read-only access safely.
What does a Supabase security audit cover?
A Lovable app runs on Supabase, either Lovable Cloud or your own project, so a Lovable code audit is largely a Supabase security audit plus a read of the code. On the Supabase side I check:
- Row level security on every table the API exposes, tested with two real accounts, not read from the policy list.
- Tenant isolation: whether a user of one company can read another company’s rows, including a user who belongs to both.
- API keys: no
service_roleor secret key in the browser bundle, and what the public key can reach. - Storage buckets: which ones are public and what the policies on
storage.objectsallow. - Exposed schemas, views that bypass RLS and definer functions callable through the API.
- Auth settings that live only in the hosted project, from leaked password protection to redirect URLs and MFA.
- Backups or point-in-time recovery.
On your own Supabase project, the free Supabase security scan reads these settings first. A Lovable Cloud project does not show up in your Supabase account, so there the two-user tenant isolation test is the free first step. In the audit I then test what a scan cannot see with real accounts and read the code that talks to the database.
What do keep, fix and rewrite mean?
- Keep: the part works and is safe. Leave it alone, even if the code is not pretty.
- Fix: the part is built the right way but has a hole or a bug that a contained change closes.
- Rewrite: the part cannot be made safe where it stands, usually because its data model is wrong.
I recommend rewriting the whole app only when the data model is wrong at the root. A full rewrite also throws away the bugs you have already found and fixed, so it is rarely the first answer.
What do you check?
- Who can reach the data: row level security or Firebase rules, tested with two real accounts rather than read from the settings screen.
- Secret keys in the browser bundle, and AI endpoints anyone can call and run up your bill.
- Sign-up, password reset and email settings left at their defaults.
- Payments: whether a webhook is verified and whether a retry charges or writes twice.
- What only shows up with real users: swallowed errors, duplicate writes and pages that load every row.
- Who holds the accounts, whether backups exist, and whether another developer could take this over.
The common holes, reproduced on a test project, are in vibe coding security risks, and the checks for a Lovable app are in the Lovable app security checklist. For what a penetration test costs, see penetration test cost in 2026.
What happens after the audit?
The verdict is yours, and you can take it to any developer. The audit does not include the fixes. If you want me to do them, that work runs on a monthly plan, and the €490 comes off your first month if you subscribe within 30 days of the audit. For an app you already know needs taking over, see project rescue.
Have a quote for the work but no audit? I also give a free second opinion on a developer’s quote.
Comparing the audit with a freelancer, a rescue shop or an agency? See who to hire to fix a Lovable app.
5.0 from 6 Upwork reviews
5.0 / 5
Comprehensive security assessment and bug fix for new website. Worked very quickly and jumped on a video call to talk me through the changes and next steps. Was super impressed and would 100% work with him again. Thanks a million!
When not to buy this
This is not a penetration test, a compliance certificate or a guarantee that the app can never be broken into. It is also not a fit for a large system run by several teams, or for a prototype with no users that you could rebuild in a weekend.
Stack
- Lovable
- Bolt
- Cursor
- Supabase
- PostgreSQL
- Firebase
- Next.js
- React
- Vite
- TypeScript
- Node.js
- Stripe
- Vercel
- Cloudflare Workers