What Lovable already checks
Lovable has its own security scan. According to Lovable's security documentation, a quick scan runs when you open the publish dialog and looks at your database access rules, dependencies and MCP server exposure. You can also start a deeper scan yourself from the Security view. Workspaces can even block publishing while critical findings are open.
Use it. It sees your project from the inside, while you build. Lovable's own docs also say that "no issues found" doesn't guarantee an app is free of risk.
Why check the live app as well
A scan inside the editor checks your project. What visitors get is the published site: the built JavaScript bundle, the server's headers, the files the host serves and the public settings of your Supabase project. Securick reads exactly that, from a public URL, with nothing to install. It works the same for apps from any builder, so you can compare a Lovable app with one you made elsewhere.
Common security mistakes in Lovable apps
1. A secret key in the front end
Lovable apps run in the browser, so anything written into the front-end code is public. Lovable's secrets feature keeps API keys out of the browser: they're encrypted and only passed to your Edge Functions. Problems start when a key is pasted straight into a component, or when a prompt asks the AI to "just make it work" with a key in the client.
2. The Supabase service key instead of the public key
Supabase gives you a public key for the browser and a secret one for servers. Supabase's docs say the secret key (and the older service_role key) bypasses Row Level Security and must never be put in a browser. If it ends up in your bundle, anyone can read and change every table.
3. Tables without the right row-level security
With Row Level Security on and no policies, the public key can't read anything. With a policy that's too broad, it can read everything. Our guide to Supabase RLS explains the difference with examples.
4. Sign-up settings left on their defaults
Email confirmation turned off, social logins that can send users back to any website, or a Site URL still set to localhost. These are settings in your Supabase project, not in your code, so they're easy to miss.
5. Missing security headers
Headers like Content-Security-Policy and HSTS protect visitors against injected scripts and downgraded connections. Whether you have them depends on where and how the app is hosted.
What Securick tests on a Lovable app
Every number below is a test in our public list of tests. The free scan runs the Free ones; Pro runs all 130.
- #5 Supabase service key exposed Free
- #111 Supabase personal access token exposed Free
- #112 Database connection string with password exposed Free
- #10 Secret values in public env variables Free
- #1 Stripe live secret key exposed Free
- #2 OpenAI API key exposed Free
- #13 JavaScript source maps public Free
- #23 Content-Security-Policy present Free
- #22 HSTS header Free
- #29 Not open to every website Free
- #30 Not open to every website with login cookies Free
- #117 Sign-ups confirm the email address Pro
- #120 Social login only returns to your own site Pro
- #121 Auth Site URL isn't localhost Pro
On a domain you verify, the Deep scan goes further, using only the public key your app already ships:
- #59 Supabase tables not readable with the public key Deep
- #60 Supabase storage buckets not listable Deep
- #147 Database functions not callable by anyone Deep
- #96 Data isolation between users Deep
- #97 User files and profiles isolated Deep
What a finding looks like
Your Supabase service key is in your website's code
Fix prompt to paste into your builder
Remove the Supabase service_role key from all front-end code and use the public (anon or publishable) key in the browser instead. Move anything that really needs the service key into a Supabase Edge Function that reads it from secrets. Then rotate the service key in Supabase, because the old one has been public.
Every finding comes with the proof of what we saw (secrets masked) so you can check it yourself. Fix prompts are part of Pro.
Free, Pro and Deep
Free
46 tests from your public URL, 2 scans a day, no sign-up. Every finding with proof.
Pro · $10 one time
30 scans within 30 days: all 130 tests, with a fix prompt for every finding and PDF reports.
Deep · part of Pro
17 more tests (147 in total) that touch your database and signed-in users, only on a domain you verify.
Questions
Does Securick replace Lovable's own security scan?
No. Keep using Lovable's scan while you build. Securick is a second, independent check of the published app from the outside: what visitors and attackers can actually load.
Do I need to connect my Lovable account or GitHub?
No. Paste your app's public address. The free and Pro scans only read what any visitor can load, plus DNS records and the public settings of your Supabase project.
Can Securick tell that my app was made with Lovable?
Often, from the lovable.app address or markers in the page. It doesn't need to: every test runs the same way whichever builder made the app.
Will the scan change anything in my Supabase database?
Free and Pro scans don't touch your database. Deep tests only run on a domain you verify, and they read with the public key your app already ships. They count rows and never store your data.