Skip to content
Qlinnt
← All checks

Security

Secret keys exposed in your JavaScript

We found what looks like real credentials shipped in your public JavaScript: . Anyone who opens the browser dev tools can read them.

What it means

An API key or private token that should live only on your server was bundled into the code sent to the browser. Client-side code is fully visible to any visitor.

Why it matters

Exposed keys get scraped by bots within hours. A leaked Stripe or cloud key can mean fraudulent charges, data theft or a hijacked account — and a Supabase service_role key bypasses all your security rules.

How to fix it

Move the secret to a server-side environment variable, rotate the exposed key immediately (assume it is compromised), and only ever ship publishable/anon keys to the browser.

Check your own site

Run the available checks on your live site and see what deserves attention.