db-schema-audit

You can audit a PostgreSQL schema for missing indexes and security issues by running SQL queries to detect unindexed foreign keys, potential PII columns, and tables lacking Row Level Security. It generates a Markdown report with scores and action items.

A database schema audit evaluates schema quality, performance, security, and data integrity. You need one before deploying new database-heavy features to catch potential bottlenecks, unencrypted PII, and missing primary keys.

Yes, you can check for unencrypted PII columns and missing Row Level Security in Supabase. The audit executes SQL queries against the PostgreSQL database to identify these specific security vulnerabilities and data integrity risks.

To check database schema best practices and naming conventions automatically, run an autonomous fast audit mode. It scans for non-compliance with naming conventions, missing primary keys, and unindexed foreign keys, returning a detailed Markdown report.

Limitations of running a schema audit on a large PostgreSQL database include potential performance overhead from executing comprehensive SQL queries. If the database is extremely large, interactive guided audits or pre-flight planning modes can help scope the analysis.

The best way to identify tables lacking Row Level Security is to perform a comprehensive schema audit. It executes targeted SQL queries to detect missing RLS policies, unindexed foreign keys, and potential PII columns, generating a scored Markdown report.