Bolt.new security audit
Bolt's Security tab flags database rules that look wrong. This check signs in as two of your users on the live app and tries to read, change and delete each other's data, then shows you the request, the response and the fix. Five working days after access.
What gets checked on your app
- Bolt Database and Supabase rules Bolt's Security tab runs the same checks as Supabase's Security Advisor, including an "RLS Policy Always True" warning. We read every policy, then test it with two real sessions, because a rule that looks fine can still let one user read another's rows.
- Vite builds Many Bolt projects use Vite, so anything named VITE_ ends up in the browser. We search the live bundle for secret keys.
- Server functions and payments Functions that accept a user id from the browser, and Stripe webhooks that trust the success page.
- Files Uploads that should be private, opened from a signed-out browser.
What you receive
- The request sent and the response received for every check
- A short video of any request where one user gets another user's data
- Findings ranked by what a stranger could do, each with the fix
- A one-page note of what was tested and what was left out
- One recheck after you apply the priority fixes
- £449 off the fix invoice if the fix starts within 14 days
See a sample report from a real test, or watch the recording of user A reading user B's note.
Questions
Is Bolt's Security tab enough?
Run it and fix what it finds. It checks rules against patterns; it does not know which rows belong to which of your users. The two-account test does.
Do you need my Bolt login?
No. We need the live URL, read-only access to the code, and your written permission. We create our own test users.
What if you find nothing?
You still get the request and response for each check. If a check in scope has none, you do not pay.
A vibe coding security checklist for Lovable, Bolt, v0 and more
The method is free. The check is the run, the evidence and the recheck. It is not a penetration test and does not certify the app as safe to launch.
Book before you launch
At checkout, add the app URL and the date you plan to turn on payments or let real users in. After payment, send read-only repository access and the signed permission. Run by David Salami. Full scope on the 5-Day Two-Account Check.