2026-11-19 · Daily security tips
Does a secret in your .env start with NEXT_PUBLIC_ or VITE_?
The prefix on an environment variable decides who can see it. In Next.js, anything starting with NEXT_PUBLIC_ is written into the browser bundle at build time. In Vite, anything starting with VITE_ is exposed to client code. AI tools often add the prefix just to make an error go away, and a secret key ends up public.
Check: open your .env and list every NEXT_PUBLIC_ or VITE_ variable. Each one should be safe for strangers to read, like a Supabase anon key or Stripe publishable key. If you see an OpenAI key, sk_live, or a service_role key, it is in your live site.
Fix: rotate that key first. Then drop the prefix and call the API from a server route or Supabase Edge Function instead.
Is your live site exposing something like this?
The free quick check looks at what your site already serves publicly: secret keys in your JavaScript, open /.env files and /.git folders, Supabase tables readable with your public key, and missing security headers. No sign-up needed.
No app handy?
No sign-up. Read-only public-resource and protocol metadata checks. No model prompts or tool execution. Scan only sites you own or are allowed to test.
Run on every deploy or use from Cursor / Claude Code via MCP →