SaaS Starter — Lovable Build
https://my-saas-app.lovable.appDate
Auditor
Score by category
Critical findings
5 issuesRow-Level Security enabled on all tables
criticalThe `profiles` and `user_data` tables have RLS disabled. Any authenticated user can read and write all rows.
Enable RLS on every user-facing table in the Supabase dashboard and add explicit USING and WITH CHECK policies.
Service role key not exposed to client
criticalThe Supabase service role key was found in client-side code (`lib/supabase.ts`). This key bypasses all RLS policies.
Move service role usage to server-side API routes only. Use the `anon` key in client-side Supabase clients.
Preview deployments do not use production secrets
highVercel Preview deployments are using Production environment variables, including the live Supabase database URL.
Create a separate Supabase project for staging and set Preview-only environment variables in the Vercel dashboard.
No secrets in `.env` committed to git
critical`.env.local` containing `SUPABASE_SERVICE_ROLE_KEY` and `STRIPE_SECRET_KEY` was found in git history.
Immediately rotate all exposed keys. Add `.env*.local` to `.gitignore` and use `git filter-repo` to purge from history.
Rate limiting on public API endpoints
highPublic-facing API routes have no rate limiting, making them vulnerable to abuse and DoS attacks.
Add Vercel Edge Middleware rate limiting or use Upstash Redis with the `@upstash/ratelimit` package.
Warnings
12Policies use `auth.uid()` correctly
Supabase / RLS
Storage bucket policies configured
Supabase / RLS
Auth session refresh handled correctly
Authentication
OAuth providers configured with correct redirect URIs
Authentication
Build output type matches deployment target
Vercel Deployment
Environment variable validation on app startup
Environment Variables
Loading states for async data
UI / UX
Responsive design on mobile devices
UI / UX
Empty states for lists and tables
UI / UX
API routes validate and sanitize input
Database / API Safety
Error monitoring (Sentry or similar)
Production Readiness
SEO: meta tags and OG images
Production Readiness
All findings
31 checks · 7 categories
| Check | Status | Severity |
|---|---|---|
Row-Level Security enabled on all tables | failed | critical |
Policies use `auth.uid()` correctly | warning | high |
Service role key not exposed to client | failed | critical |
Anon key restrictions are correctly scoped | passed | medium |
Storage bucket policies configured | warning | high |
Email confirmation required on sign-up | passed | medium |
Auth session refresh handled correctly | warning | medium |
Protected routes redirect unauthenticated users | passed | high |
OAuth providers configured with correct redirect URIs | warning | medium |
Password reset flow functional | passed | low |
Environment variables set in Vercel dashboard | passed | high |
Build output type matches deployment target | warning | medium |
Custom domain and SSL configured | passed | low |
Preview deployments do not use production secrets | failed | high |
No secrets in `.env` committed to git | failed | critical |
Public env vars use `NEXT_PUBLIC_` prefix only where needed | passed | medium |
Environment variable validation on app startup | warning | medium |
Loading states for async data | warning | medium |
Error boundaries prevent full-page crashes | passed | high |
Responsive design on mobile devices | warning | medium |
Empty states for lists and tables | warning | low |
Form validation feedback | passed | medium |
Database queries use parameterized inputs | passed | critical |
API routes validate and sanitize input | warning | high |
Rate limiting on public API endpoints | failed | high |
Database connection pooling configured | passed | medium |
Error monitoring (Sentry or similar) | warning | medium |
Analytics tracking implemented | passed | low |
SEO: meta tags and OG images | warning | low |
Security headers configured | passed | high |
GDPR / Privacy policy in place | passed | medium |
Want your own app audited?
This demo shows the format. Real audits go deeper — into your actual codebase, RLS policies, and deployment config.