Bolt.new security check for apps you built with Bolt
Bolt apps are typically a Vite front end that talks straight to a backend service such as Supabase, so a secret or a loose policy ends up in code every visitor downloads. ScanAnt recognises Bolt-hosted sites, scans the public bundle and, after ownership proof, tests the backend access rules.
Free, no signup. We only read what your site already shows every visitor.
What we check
Each item is tagged with the scan that reports it. The quick scan is free and needs no signup. The others run only on sites you have proved you own.
Bolt platform detection
Quick scanWe recognise bolt.host sites and Bolt markers in the page, then pick the checks that fit a browser-first app.
Secrets in the Vite bundle
Quick scanKeys exposed through VITE_ variables or pasted into components: AI, payment, mail, database and cloud keys, shown masked.
Source maps
Quick scanWhether your original component code is downloadable from the deployed site.
Security headers
Quick scanStatic hosting sends few protective headers, so we check HSTS, CSP, clickjacking protection, nosniff and Referrer-Policy.
Client-side trust
Quick scanPlans, prices or roles decided in browser code, and admin routes that ship to every visitor.
Supabase or Firebase access rules
Verified scanIf the app uses them, whether anonymous visitors can read tables, collections or storage files.
Exposed files and API paths
Verified scanPublic .env files, backups, API documentation and debug paths on the deployed host.
Uploaded project code
Code scanHard-coded keys, committed env files, server secrets in public variables, and API routes without authentication in a ZIP of the project.
- Quick scan: No signup. Reads only what every visitor receives.
- Verified scan: After you prove you own the site. Read-only.
- Code scan: You upload your project as a ZIP.
No scan can promise to find every problem. A clean result means no known problems were found on what the scan could see.
Common mistakes
Putting a secret into a VITE_ variable
Vite inlines every VITE_ value into the bundle that the browser downloads.
Calling an AI or payment API from the front end
The key travels with each request and can be copied in seconds.
Deploying with source maps enabled
They turn minified code back into readable source.
Relying on the preview for access control
Everything works for the owner, which says nothing about a stranger with the public key.
How to fix it
Move secret calls into a backend function and keep only publishable keys in the front end.
Rotate any key that appeared in code, then turn off production source maps in your Vite config.
Add security headers through your host's config file or proxy.
Enable and test row-level security or Firebase rules, with a second account.
Use the fix prompt of each finding in Bolt, and rescan to confirm.
Questions
Does it work if I deployed Bolt to my own domain?
Yes. The checks work on any reachable URL. For deeper checks you prove ownership of that exact host with a token file, a meta tag or a DNS record.
Which backend does it expect?
None specifically. It detects Supabase and Firebase, and for any other API it checks exposed files, headers and public code.
Is a VITE_ key always a problem?
No. Publishable keys such as a Supabase anon key are meant to be public. The problem is a secret key, which the report flags separately.
Can I keep a record of fixes?
Each report has a share link and PDF, and a rescan after your changes shows which findings are gone.
Related checks
Lovable security check: is your Lovable app safe to launch?
Supabase RLS, leaked keys and client-side trust in apps built with Lovable.
Open →Find API keys and secrets exposed on your website
Leaked Stripe, OpenAI, AWS and database keys in public JavaScript.
Open →Supabase security check: RLS, storage and auth
What anyone can read or write with your anon key, and whether service_role leaked.
Open →
Run the scan now
Free for any public site, no signup. Need the verified, deep or code scan? Choose the level on the scan page.
Choose a scan level →