Bolt security scanner
Bolt turns a prompt into a working full-stack app in minutes, and most Bolt apps keep their data in Supabase. The settings that keep that data private are exactly the ones a fast build tends to skip. This page explains what breaks on Bolt and scans your live app now.
Scan your Bolt app
What it means
Anyone can read this table without logging in. That can be deliberate, such as reference data or a public directory, or a missing access policy; only you can say which. xlogs read one row's column names and kept none of its values.
Why AI tools cause it
Supabase only limits who can read a table once you turn on Row Level Security (RLS) and write access rules for it. An AI tool can build a working app without doing that, and a table without RLS, or with a policy that lets everyone read, answers anonymous requests.
How xlogs checks it
xlogs finds your public Supabase URL and anon key in your app (the same ones your frontend uses), asks the database for its table list, reads one row from each listed table as an anonymous user, and flags any that return rows. Hosted Supabase refuses that list to public keys, so on a hosted project the result says the tables could not be checked. Read-only: it never writes or deletes.
What to check first on a Bolt app
Three things worth checking on any AI-built app apply to Bolt apps too: a Supabase database readable by anyone, a secret key shipped in the browser code, and missing security headers. Bolt gets the app running; these are settings to check yourself.
None of them are visible while you use the app. It looks finished and works fine. The scan below checks your live app the way an outsider would.
The top Bolt security issues to check
- Publicly readable Supabase database (Row Level Security off)
- An API key or service key exposed in the client bundle
- Missing security headers (CSP, HSTS, X-Frame-Options)
- Source maps that let anyone download your original code
How to fix it
The goal: Row Level Security is enabled on every table, and each table returns rows only to the users it is meant for: a private table answers no anonymous request, and a table that is public on purpose has a read policy that says so.
- Decide whether the affected spot is meant to be readable without a login
- If it is not, enable Row Level Security (RLS) on the affected spot and add a policy so only the users allowed to see a row can read it
- If it is, keep it public on purpose, and record that decision so a review does not reopen it
- Do not switch on a restrictive policy for a table your public pages read without a replacement read policy, or those pages stop working
- Re-check that an anonymous request returns what you decided it should
In my app (the spot the scan shows): anyone can read this table; confirm that is deliberate. Please make this true: Row Level Security is enabled on every table, and each table returns rows only to the users it is meant for: a private table answers no anonymous request, and a table that is public on purpose has a read policy that says so. Steps: Decide whether the spot the scan shows is meant to be readable without a login; If it is not, enable Row Level Security (RLS) on the spot the scan shows and add a policy so only the users allowed to see a row can read it; If it is, keep it public on purpose, and record that decision so a review does not reopen it; Do not switch on a restrictive policy for a table your public pages read without a replacement read policy, or those pages stop working; Re-check that an anonymous request returns what you decided it should. Then tell me exactly what you changed, and do not print any secret values back to me or write one into a commit message, a pull request description or a log.
Then verify: After you decide and deploy, xlogs repeats the same anonymous read of each table the database lists and reports what comes back: a table you made private should no longer return rows, and one you keep public still will. If the table list is refused, it says the tables could not be checked.
Full step-by-step fix guide, with a copy-paste block for each AI tool →
Common questions
Does Bolt make my app secure by default?
No. Bolt gets your app running, but the database access rules and security headers your deployed app serves are yours to check. Those decide who is allowed to read your data. A working Bolt app can still let anyone read its tables.
How do I check if my Bolt app is safe?
Paste your live Bolt URL into the scanner above. It reads the JavaScript your app ships, checks your response headers, and asks your database, as an anonymous user, whether its tables return rows. You get a plain-English report and a fix.