Checklist
Lovable + Supabase + VercelAudit ReportComplete

SaaS Starter — Lovable Build

https://my-saas-app.lovable.app

Date

2026-06-04

Auditor

Pedro Alves
72/100
Grade C
Needs Work
+5 pts from last audit
72/100
Audit Score
Needs Work
3
Critical Issues
Fix before launch
7
Warnings
Should address soon
18
Checks Passed
of 31 total

Score by category

Supabase / RLS
2✗2⚠
20%
Authentication
2⚠
60%
Vercel Deployment
1✗1⚠
50%
Environment Variables
1✗1⚠
33%
UI / UX
3⚠
40%
Database / API Safety
1✗1⚠
50%
Production Readiness
2⚠
60%

Critical findings

5 issues

Row-Level Security enabled on all tables

critical

The `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

critical

The 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

high

Vercel 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

high

Public-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

12

Policies use `auth.uid()` correctly

Supabase / RLS

high

Storage bucket policies configured

Supabase / RLS

high

Auth session refresh handled correctly

Authentication

medium

OAuth providers configured with correct redirect URIs

Authentication

medium

Build output type matches deployment target

Vercel Deployment

medium

Environment variable validation on app startup

Environment Variables

medium

Loading states for async data

UI / UX

medium

Responsive design on mobile devices

UI / UX

medium

Empty states for lists and tables

UI / UX

low

API routes validate and sanitize input

Database / API Safety

high

Error monitoring (Sentry or similar)

Production Readiness

medium

SEO: meta tags and OG images

Production Readiness

low

All findings

31 checks · 7 categories

3 failed 7 warnings 18 passed
CheckStatusSeverity
Row-Level Security enabled on all tables
failedcritical
Policies use `auth.uid()` correctly
warninghigh
Service role key not exposed to client
failedcritical
Anon key restrictions are correctly scoped
passedmedium
Storage bucket policies configured
warninghigh
Email confirmation required on sign-up
passedmedium
Auth session refresh handled correctly
warningmedium
Protected routes redirect unauthenticated users
passedhigh
OAuth providers configured with correct redirect URIs
warningmedium
Password reset flow functional
passedlow
Environment variables set in Vercel dashboard
passedhigh
Build output type matches deployment target
warningmedium
Custom domain and SSL configured
passedlow
Preview deployments do not use production secrets
failedhigh
No secrets in `.env` committed to git
failedcritical
Public env vars use `NEXT_PUBLIC_` prefix only where needed
passedmedium
Environment variable validation on app startup
warningmedium
Loading states for async data
warningmedium
Error boundaries prevent full-page crashes
passedhigh
Responsive design on mobile devices
warningmedium
Empty states for lists and tables
warninglow
Form validation feedback
passedmedium
Database queries use parameterized inputs
passedcritical
API routes validate and sanitize input
warninghigh
Rate limiting on public API endpoints
failedhigh
Database connection pooling configured
passedmedium
Error monitoring (Sentry or similar)
warningmedium
Analytics tracking implemented
passedlow
SEO: meta tags and OG images
warninglow
Security headers configured
passedhigh
GDPR / Privacy policy in place
passedmedium

Want your own app audited?

This demo shows the format. Real audits go deeper — into your actual codebase, RLS policies, and deployment config.