Supabase · public keys
Supabase API keys: publishable vs secret, anon vs service_role
Publishable/anon keys are safe in browser code; secret/service_role keys bypass RLS and belong on the server. Compare formats, roles, and migration.
Updated
Guides
Direct answers, reproducible examples, provider-aware distinctions, and an explicit line between public evidence and authorized testing.
Supabase · public keys
Publishable/anon keys are safe in browser code; secret/service_role keys bypass RLS and belong on the server. Compare formats, roles, and migration.
Updated
Stripe · API key exposure
Stripe pk keys belong in client code; sk and rk keys stay on the server. Compare test/live prefixes and what to do if a privileged key is exposed.
Updated
Firebase · public API keys
A Firebase API key in web or mobile code is usually public by design. Verify API restrictions, Security Rules, App Check, and separate secret credentials.
Updated
Supabase · Row Level Security
Review Supabase Row Level Security with an evidence-led checklist for grants, policies, tenant boundaries, views, functions, claims, and authorized role tests.
Updated
Supabase · privileged key exposure
A practical response plan for a Supabase service_role or secret key exposed in browser code, a repository, logs, or another public location.
Updated
Supabase · API key location
Find Supabase publishable, secret, anon, and service_role keys in the current dashboard, then choose the right key for browser or server code.
Updated
Lovable · security scan
What Lovable’s built-in security tools cover, what an independent outside view adds after deployment, and which questions still require source or human review.
Updated
all stacks · launch checklist
A staged security checklist for AI-built apps: public deployment evidence first, then source-backed validation and human review for sensitive workflows.
Updated