securick

Sample report

What a Securick report looks like

An example with made-up data, not a real customer's scan.

Fix these first3 to fix
  • Your Stripe secret key is visible to anyone

    Found in your site's code

    Critical
  • Other websites can read your app's data

    Your server trusts any website that asks

    Medium
  • No protection against injected scripts

    A security setting your host can add is missing

    Medium
One problem, opened Critical

Your Stripe secret key is visible to anyone

Anyone who opens your site can copy this key and use your Stripe account: give refunds, create charges or download your customer list.

Proof: what we saw
1. We opened your site's code file, like any visitor's browser does:
GET your-app.lovable.app/assets/index-4f2a.js
2. Inside it, your live secret key (we hide most of it):
Stripe("sk_live_51N••••••••••Qx2")
How to fix it: copy this into your AI builder

Move the Stripe secret key out of the front end. Create a Supabase Edge Function that reads STRIPE_SECRET_KEY from environment secrets and creates the payment there. Call that function from the client instead of using the key. Then roll the exposed key in the Stripe dashboard, because it is already public.

How to read it

  • Fix these first lists the problems that matter most, worst first, in plain words.
  • Proof shows exactly what we requested and what came back, with secrets masked, so you can check it yourself.
  • How to fix it is a prompt you paste into Lovable, Bolt or Cursor to fix that one problem.
  • A real report also says what the scan covered and lists what it didn't, so a clean result never claims more than it tested.

Run a free scan See Free and Pro