[hiabhee]

Summary

• Enable RLS on application-owned tables in the exposed public schema.
• Revoke direct table and sequence privileges from PUBLIC, anon, and authenticated.
• Remove those grants from future tables and sequences created by the migration role.
• Leave objects owned by extensions or other roles unchanged. Server-side Prisma retains access as the database owner.

Validation

• Applied the migration to an isolated temporary PostgreSQL database with representative anon, authenticated, service_role, and extension-owner roles.
• Confirmed RLS is enabled, anonymous/authenticated privileges are revoked, RLS returns zero rows even after a SELECT grant, server-role access is retained, future public objects receive no API-role grants, and a foreign-owner object is unchanged.
• npx prisma validate --schema prisma/schema.prisma passed in the main checkout.

The production Supabase project was not modified. Apply this migration, then refresh the Supabase advisors to confirm the findings are cleared.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
arch-draw	Ready	Preview	Nov 10, 2026 6:54pm UTC

[coderabbitai]

Important

• Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: d20d12bf-9fdb-4178-86da-1326de497f71

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn