r/Supabase • • 27d ago

tips Reminder: new tables will require explicit API grants from October 30

8 Upvotes

Starting October 30, newly created tables in the public schema on existing Supabase projects will need explicit GRANT statements to be accessible through the Data and GraphQL APIs, including via supabase-js.

Existing tables keep their current grants and will continue working. RLS behavior is unchanged, and direct Postgres connections aren’t affected.

If your migrations or AI tools create tables, make sure they include the appropriate grants alongside your RLS policies.

Full details and SQL examples


r/Supabase • • 18h ago

tips Non-technical founder: where do I find someone for a one-off code + security review of an AI-built app?

3 Upvotes

I’m a solo, non-technical founder and I’ve built a B2B web app using Claude Code as my “engineer”. It’s a multi-tenant SaaS for professional services firms: each customer firm is a separate tenant in one shared database. It’s working end to end and I’m hoping to pilot it with one firm (around 5 users).

Before any real customer data goes in, I want a proper developer to spend a focused day on it and tell me honestly:

  1. Is it secure? Mainly: can one tenant ever see another tenant’s data?

  2. Is the code actually well built, or is it a vibe-coded mess I’ll regret building a business on?

Stack: Next.js (App Router, server actions), TypeScript, Supabase (Postgres with row level security, magic-link auth, Storage), Vercel. It’s about 9,500 lines plus 17 SQL migrations. There’s a test suite and CI, and I’ve run an automated audit plus an AI review, but I don’t trust an AI to mark its own homework.

I’ve got a written brief and I’m happy to pay a fixed fee for one day (budget roughly AUD $1,000–1,500). I’m based in Sydney but remote is fine.

My questions:

  • Where would you look for someone like this? Platforms, communities, agencies?

  • What should I ask to separate people who genuinely know Supabase RLS from people who’ll skim it?

  • Is one day realistic for this size of codebase, or am I kidding myself?

Thanks!


r/Supabase • • 1d ago

other Supabase or Cloudflare for an iOS game app? Need some advice.

7 Upvotes

Hey everyone!
I’ve been working on an iOS game app for a while now, and I’m trying to figure out which backend would be the right choice before I go further.
I need backend support for a few things:
User authentication and login
Cloud database and storage
Player profiles and game progress
Global leaderboards to compare scores
Basic backend APIs and related functionality
I’m relatively new to backend infrastructure, so I’d prefer something that’s easy to integrate with Swift/SwiftUI and doesn’t require me to manage too much infrastructure myself.
I’ve been looking at Supabase and Cloudflare, but I’m a bit confused about which direction to take.
For someone building an iOS game independently, what would you recommend?
Is Supabase enough to handle everything, or does Cloudflare offer some advantages worth considering?
Also interested in hearing about free-tier limitations, pricing as users grow, and any issues you’ve faced in production.
Would appreciate advice from anyone who’s built something similar!


r/Supabase • • 16h ago

auth Prevent gmail message threading for reset emails

Post image
1 Upvotes

A user raised an issue around password reset. They did a reset, got distracted (so the link expired) then did another reset... but they couldn't find the second link in their gmail.

Fair enough, it's right there under the ellipsis ('...') but it's confusing, you need to look at the times to see what is the latest, then click the '...' to expand the second email and click the link... it's all work.

Can I prevent the threading? I think If I put something like the reset token (which changes per attempt) in the subject of the email, it might prevent threading. But I don't think I can customise the subject like that? Can I put variables in the subject?


r/Supabase • • 1d ago

database Supabase

20 Upvotes

I am new to Supabase. Should I create my own database or use the default “Postgres” database? According to the documentation, customized databases are not supposed by the dashboard, auth, etc. I am intended to use the database for the backend of an App. I also want the flexibility to move to other platforms down the road.

Thanks!


r/Supabase • • 1d ago

other Reloops v0.3.1: live HTML5 ad review, built on Supabase [Update]

8 Upvotes

A while back I shared Reloops here, an open-source (AGPL) client review tool for videos and other creative files, built on Supabase Auth, Postgres, Storage and Edge Functions

(original post). Here's what's new.

New in v0.3.1: HTML5 banners play live

Reviewing HTML5 ads usually means emailing zips and hearing "it won't open on my end."

Now you upload the .html and it plays right in the review page:

  • Pinned comments, drawings and zoom work on the live ad, including from share links where guests comment without an account

  • It runs in an iframe with sandbox="allow-scripts" only, so an uploaded ad can't touch the app's page, cookies or the Supabase session in storage

  • The ad size is detected from <meta name="ad.size"> or the page CSS, with IAB presets (300×250, 728×90, etc.) as overrides

  • One click opens a code view of the source (Shiki, lazy-loaded)

Self-hosting is still one command: docker compose up starts the app and runs the Supabase stack locally through the CLI.


r/Supabase • • 2d ago

other Can I get charged thousands of dollars if my Supabase Free project gets attacked?

8 Upvotes

I'm currently using the Supabase Free Plan for a personal application. I'm the only user, and under normal circumstances, I will never come close to the free tier usage limits.

However, I'm concerned about a potential scenario where someone attacks my application (DDoS, automated API requests, excessive database queries, etc.) and causes my project to exceed its free tier quotas.

My main concern is receiving an unexpected bill of hundreds or thousands of dollars because of an attack I didn't initiate.

According to Supabase's official documentation:

"However, you will not be charged while using the Free Plan."

I also understand that the Spend Cap feature is only available on the Pro Plan.

My questions are:

If someone attacks my Free Plan project and causes me to exceed the quotas (Egress, Database, Storage, Edge Functions, etc.), can Supabase charge me anything?

Will the project simply be restricted, paused, or become unavailable until the next billing cycle?

Is there absolutely no risk of automatic charges or being moved to a paid plan?

Has anyone actually experienced this situation on the Free Plan?

For context, I have no payment method registered with Supabase and no paid subscriptions or add-ons.

I understand that an attack could make my application unavailable. My concern is strictly about unexpected financial charges.

This is just a hobby app that helps me in my personal day to day.

Thank you!!!


r/Supabase • • 2d ago

tips AI-built apps on Supabase: how do you keep the database safe when the AI adds features after launch?

7 Upvotes

For people who built their app with Lovable, Bolt, Cursor or similar on Supabase and now have real users.

Shipping the first version is the easy part. Adding features later is harder, because the AI often changes the database too: renaming columns, changing tables, updating RLS policies.

I asked experienced devs about this in another sub, and a few habits came up again and again:

- take a snapshot or pg_dump right before any risky migration

- set a lock_timeout at the top of migrations, so a blocked change fails fast instead of freezing the app

- never drop or rename a column in one step: add the new one, move the data, drop the old one later

- if data gets damaged, restore the backup into a separate schema and copy back only the affected rows, so newer data isn't lost

I'm curious what people building with AI tools actually do. What's working for you? And if something went wrong, what happened, how did you fix it, and did you lose any data?


r/Supabase • • 2d ago

database What are the disadvantages of using drizzle with supabase?

1 Upvotes

Hello, I am considering drizzle for a project because having to write and maintain RPCs for any somewhat complex query is making me go crazy.

I want to know what problems you faced when using drizzle that I might not realise until I am way too invested.


r/Supabase • • 3d ago

edge-functions I can't see my code of edge functions in the dashboard

Post image
3 Upvotes

Luckily, it's still working. But I have to edit a function which I cannot access. I tried download but the zip file is empty. Anyone who know how to handle this?


r/Supabase • • 3d ago

other Will this stat affect the project's functionality?

Post image
1 Upvotes

Actually i rarely use logs. Can we enable or disable this log?


r/Supabase • • 4d ago

tips I made a CLI that turns a Supabase schema into an Angular admin, with RLS doing all the authorization

2 Upvotes

I am the maintainer of Pidrang, an open-source Angular admin framework with a Supabase data and auth provider built on supabase-js.

In a new Angular app, npx pidrang init reads your schema, lets you pick tables and actions, and generates list, create, show and edit pages with a sign-in page if you selected it. You then put your publishable key in the environment files. The secret key, if you use it, is only used to read the schema and never goes into the app.

Pidrang does no authorization itself. Every read and write goes through PostgREST, so your RLS policies decide. Signed out, the generated pages hide Create, Edit and Delete. Errors come back with a category (`unauthenticated`, `forbidden`, `not-found`), so the UI can ask the user to sign in instead of showing a raw PostgREST message.

It is pre-1.0 and every table needs an id primary key. I am looking for people to try it on a real schema and tell me what breaks, and how you handle admin access with RLS today.

Live demo: https://pidrang.dev/demo-material/?utm_source=reddit&utm_medium=social&utm_campaign=launch

Getting started: https://pidrang.dev/docs/getting-started?utm_source=reddit&utm_medium=social&utm_campaign=launch

Repo: https://github.com/pidrang/pidrang


r/Supabase • • 5d ago

database Multi-tenant RLS in Supabase: keep the role on the org membership, not on the user

2 Upvotes

A common multi-tenant Supabase setup: the role (owner, admin, member) sits on the user, in a profiles column or user_metadata, and the policy checks "is this user an admin?" and "is this user in the row's org?" separately. Someone who's an admin in Org A and a plain member in Org B passes both checks on Org B's rows, so they get admin rights there too.

user_metadata adds a second problem: the Supabase docs say users can change it themselves, so it shouldn't drive authorisation. The RBAC guide's user_roles table also has no org column, which suits global roles but not per-tenant ones.

The fix is a membership row (user_id, org_id, role) checked in one place. A security definer helper in a schema not exposed through the Data API also avoids policy recursion on memberships. The update policy needs a select policy next to it, or any update that reads the row (a where clause, amount = amount + 1, returning) matches 0 rows:

create schema if not exists private;

create function private.has_org_role(p_org uuid, p_roles text[])
returns boolean
language sql
stable
security definer
set search_path = ''
as $$
  select exists (
    select 1 from public.memberships m
    where m.org_id = p_org
      and m.user_id = auth.uid()
      and m.role = any (p_roles)
  );
$$;

create policy "org members read invoices"
  on public.invoices
  for select
  to authenticated
  using ( private.has_org_role(org_id, array['owner', 'admin', 'member']) );

create policy "org admins update invoices"
  on public.invoices
  for update
  to authenticated
  using ( private.has_org_role(org_id, array['owner', 'admin']) )
  with check ( private.has_org_role(org_id, array['owner', 'admin']) );

To check it in the SQL editor, pick a user who's admin in Org A and member in Org B, then run begin;, set local role authenticated; and set local request.jwt.claim.sub = '<user id>';. Updating an Org A invoice should match 1 row and an Org B invoice 0 rows. Finish with rollback;.

For B2B apps on Supabase: do your org roles live in a table like this or in JWT claims via the custom access token hook, and how do you handle the delay before a role change reaches the token?

Edit: good additions in the comments. Add an index on memberships (user_id, org_id), and on big tables put org_id in (select org_id from public.memberships where user_id = (select auth.uid())) in the policy so the function isn't called for every row (that needs a select policy on memberships for the user's own rows). If you revoke execute on the helper from public, grant it to authenticated or the policy fails.

Edit 2: if the code block stops at the org line for you, the full where clause is where m.org_id = p_org and m.user_id = auth.uid() and m.role = any (p_roles).


r/Supabase • • 6d ago

realtime Built a daily game on Supabase: server-verified scoring, an RLS recursion gotcha, Stripe entitlements

1 Upvotes

I’m the dev (https://duel.earth). Things I learned along the way:

  • Postgres recomputes every score from its own copy of the puzzle, so clients only send raw guesses.

  • An RLS policy on my results table queried its own table and caused infinite recursion. A security-definer helper fixed it.

  • The Stripe webhook is the only writer of entitlements. The client reads its own subscriptions row and caches it for three days so premium works offline.

  • Daily reminders run from an hourly pg_cron job calling an Edge Function. The pg_net call needed timeout_milliseconds := 120000.

Overall great learning experience. Questions and feedback welcome!


r/Supabase • • 6d ago

tips An "own row" policy let any signed-in user read other accounts' data. The pattern, the fix, and a query to check your project

2 Upvotes

*Edited: reworded the framing after good feedback in the comments. The profiles policy is the bug, not "the combination".*

I found this in LabStock, an open-source inventory app built on Supabase by a Turkish developer (that's why the column is called `gozlemci_of`, "observer of"). I reported it privately in October, it was fixed on Nov 7, and he said I could write about it.

**The setup**

```sql

-- users manage their own profile row

create policy profiles_self on profiles for all to authenticated

using (id = auth.uid()) with check (id = auth.uid());

-- observers can read the stock of the account they observe

create policy stock_observer_read on stock_items for select to authenticated

using (exists (

select 1 from profiles p

where p.id = auth.uid() and p.gozlemci_of = stock_items.owner

));

```

`gozlemci_of` was meant to be set only by a SECURITY DEFINER function that checks an invite code.

**The bug**

The read policy does exactly what it says. The problem is the write side: `profiles_self` pins writes to your own row, but RLS picks rows, not columns. The table had the old default grants, so `authenticated` could update every column on its own row, `gozlemci_of` included. That means you could skip the invite code entirely:

```js

await supabase.from('profiles')

.update({ gozlemci_of: '<another user id>' })

.eq('id', myUserId)

```

It's still your own row, so it passes. From then on the observer policy shows you the other user's stock, prices, suppliers and BOMs. User IDs were easy to collect from a shared catalogue table.

The rule: **any column that another policy reads to grant access must not be writable by the client.** It's a permission, not a preference. This isn't Supabase-specific either; plain Postgres with RLS behaves the same.

Side note: since Oct 30 new tables get no Data API grants, but the common fix for the 42501 error (`grant select, insert, update, delete on profiles to authenticated`) puts the table-wide update right back.

**The fix**

Option 1, column grants. Revoke the table-wide write, then grant back only the columns users should edit:

```sql

revoke insert, update on public.profiles from anon, authenticated;

grant insert (id, name, phone) on public.profiles to authenticated; -- your editable columns

grant update (name, phone) on public.profiles to authenticated;

```

`revoke update (gozlemci_of)` on its own does nothing while the table-wide grant exists, which is why the revoke comes first. The SECURITY DEFINER function can still write the column.

Option 2, a trigger (what LabStock used). It lets users clear the link but never set it themselves:

```sql

create function public.guard_observer_link() returns trigger

language plpgsql as $$

begin

-- inside a SECURITY DEFINER function current_user is the owner,

-- so the invite-code function can still set the link

if current_user in ('authenticated', 'anon')

and new.gozlemci_of is not null

and (tg_op = 'INSERT' or new.gozlemci_of is distinct from old.gozlemci_of) then

raise exception 'Observer links can only be set with an invite code';

end if;

return new;

end $$;

create trigger guard_observer_link

before insert or update on public.profiles

for each row execute function public.guard_observer_link();

```

Either way, review existing links afterwards. A fix doesn't undo a link someone already made.

**Check your own project**

This lists columns `authenticated` can update that a policy on another table mentions. Run it in the SQL editor:

```sql

with writable as (

select c.relname as table_name, a.attname as column_name

from pg_attribute a

join pg_class c on c.oid = a.attrelid

join pg_namespace n on n.oid = c.relnamespace

where n.nspname = 'public' and c.relkind in ('r', 'p')

and a.attnum > 0 and not a.attisdropped

and a.attname not in ('id', 'user_id', 'created_at', 'updated_at')

and has_column_privilege('authenticated', a.attrelid, a.attnum, 'UPDATE')

)

select w.table_name, w.column_name, p.tablename as checked_by_table, p.policyname

from writable w

join pg_policies p

on p.schemaname = 'public'

and p.tablename <> w.table_name

and concat_ws(' ', p.qual, p.with_check) ~ ('\m' || w.column_name || '\M')

and concat_ws(' ', p.qual, p.with_check) ~ ('\m' || w.table_name || '\M')

order by 1, 2;

```

A row in the result needs a closer look, not necessarily a fix. It matters when users can also write their own row in that table. The query can't see checks hidden inside helper functions like `is_member()`, so read those too.

Column names worth a second look: `team_id`, `org_id`, `manager_of`, `linked_account`, `shared_with`.

One more review tip from the comments (thanks u/Inner_Storage_3374): permissive policies are OR'd together, so for any table with more than one policy per command, ask whether each one would still be fine as the only rule.

Full write-up: https://www.guardlayer.io/blog/supabase-rls-own-row-policy-case-study

Disclosure: I build GuardLayer, which checks for this now. The query above does the same job for free.


r/Supabase • • 7d ago

database [Help] Next.js 16 + Supabase — Database returns 3 vehicles, but website displays 0. What am I missing?

7 Upvotes

Hey everyone,

I’m relatively new to Next.js and Supabase, and I’ve been troubleshooting an issue with a car rental application I’m building.
I’m using an existing GitHub template called RentInfra, which I’ve cloned locally and am customizing into my own transportation and luxury vehicle rental platform.
I’ve spent quite a bit of time troubleshooting this and would appreciate guidance from anyone familiar with Next.js, Supabase, or this particular template.
Current development environment
Framework: Next.js 16.3.8 (App Router)
Language: TypeScript
Backend/Database: Supabase (PostgreSQL)
Authentication: Supabase Auth
Operating system: Windows 10
Terminal: Windows PowerShell
Package manager: npm
Hosting: Local development (localhost:3000)
Repository: RentInfra template cloned from GitHub

The problem
My application starts successfully using:
npm.cmd run dev
The website loads, navigation works, and the frontend styling renders correctly.
However, when I navigate to:
http://localhost:3000/cars
The page displays:
“Nothing available in this category right now.”
It also shows 0 cars available, even though my Supabase database contains three active vehicles.
What I’ve already verified

1. Supabase connection
My .env.local contains the following variables:
NEXT_PUBLIC_SUPABASE_URL
NEXT_PUBLIC_SUPABASE_ANON_KEY
SUPABASE_SERVICE_ROLE_KEY
NEXT_PUBLIC_SITE_URL
All four were confirmed to load successfully.
I also discovered and corrected an incorrectly formatted Supabase URL that previously included /rest/v1/.

2. Database records
I queried the public.cars table directly through Supabase SQL Editor.
Three vehicles exist:
Renault Clio
Toyota RAV4
Mercedes-Benz C-Class
All three have:
is_active = true
is_available = true

3. Independent Supabase API test
Using Node.js and @supabase/supabase-js, I successfully retrieved all three vehicles:
const db = createClient(
process.env.NEXT_PUBLIC_SUPABASE_URL,
process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY
);

const { data, error } = await db
.from('cars')
.select('make,model,is_active,is_available');
Result:
VEHICLES FOUND: 3
No errors.
This suggests my public API credentials and basic database access are working.

Where I suspect the issue is
The actual Next.js /cars page uses a server-side Supabase client:
import { createClient } from '@/lib/supabase/server';

const supabase = await createClient();

let query = supabase
.from('cars')
.select('*, car_images(*), price_lists(*, price_list_discounts(*))')
.eq('is_active', true);

const { data: cars } = await query.order('created_at');
Unlike my successful standalone test, this query also retrieves related records from:
car_images
price_lists
price_list_discounts
The page currently doesn’t capture or log the query error. If the query fails, the UI may simply display an empty fleet.

Additional setup information
The RentInfra README instructs users to run eight SQL migrations in sequence:
001_schema.sql through 008_booking_signatures.sql
I previously executed the migration scripts manually through Supabase SQL Editor, but I haven’t yet verified that every migration was applied correctly.
I also haven’t fully verified the relationships and permissions for the pricing and image tables.

What I need help with
I’m trying to determine:
Could a missing foreign key, table relationship, or RLS permission cause the nested Supabase query to fail even though the basic cars query succeeds?
Could the Next.js server-side Supabase client be using a different authentication context or configuration from my standalone Node.js test?
What’s the most efficient way to verify whether all eight migrations were applied correctly without rerunning them?
What debugging steps would you recommend to isolate the problem before modifying the application?
My immediate goal is simply to get the three existing vehicles to display on the /cars page.
I’m not trying to rebuild the application or change frameworks. I’d prefer to identify the actual configuration or query issue.
I’m comfortable following terminal instructions, but I’m still learning the development side of things.
Any guidance would be appreciated. Thanks in advance!


r/Supabase • • 7d ago

tips Supabase Security findings why RLS is only 25% of the issues

Thumbnail
oneleet.com
1 Upvotes

r/Supabase • • 7d ago

database How has vector or hybrid search on Supabase worked for you in production?

3 Upvotes

If you’re running semantic search with pgvector, full-text search, or a combination of both on Supabase, how has it held up as your app has grown?

I’m especially curious about search sharing the database with regular app reads and writes, or bulk imports and updates running while users are searching. Have you noticed contention? If so, what helped—query/index tuning, more compute, or moving search elsewhere?

If you moved search out, how are you keeping the data in sync, and has the tradeoff been worth it? Experiences where everything works well on Supabase are equally welcome. Rough data size and compute specs would be helpful if you have them handy.

For context, I’m building LambdaDB, a search database. We’re exploring continuously syncing Supabase tables to LambdaDB so apps can keep their writes in Supabase and run search in LambdaDB. Before building that integration, I’m planning to test these workloads, including whether tuning or scaling Supabase is enough, and share the setup and results here.


r/Supabase • • 7d ago

tips Real-world takeaway building full-stack apps with Lovable + Supabase (where it shines vs. where it hits a wall)

Thumbnail reddit.com
0 Upvotes

Over the past few months, I’ve used Lovable to prototype and ship production web tools and SaaS setups integrated with Supabase (auth, RLS, Edge Functions).

A lot of posts around AI app builders either hype them up as magic or dismiss them entirely. Here is an honest, practical breakdown of what the workflow actually looks like in production:


r/Supabase • • 7d ago

database RockxyBase: a native Mac Power BI alternative that turns your Supabase queries into dashboards, safely read-only by default

1 Upvotes

Hi everyone. I'm Stephen, and I build RockxyBase.

RockxyBase is a native Mac app that combines a database GUI with a BI workspace. You connect to Postgres, write SQL, check the rows, and turn the result into charts and a Report that still links back to the query behind every number. If you have been looking for a Power BI alternative for Mac or a Tableau alternative for Mac that starts from SQL, that is the idea.

What it does for Supabase today:
- Paste the connection string from the Connect dialog. RockxyBase stores it with verified encryption and recognizes the Supabase password placeholder.
- It explains pooler ports and IPv6-only hosts instead of failing with a vague error.
- Connections open read-only by default. Writes can require Touch ID, and DROP, TRUNCATE, or UPDATE/DELETE without WHERE stop with a row estimate first.
- Every schema change shows its SQL before it runs.

The BI side, shipped in the 0.3.0 public beta:
- Bar, Line, Combo, Heatmap, Treemap, Waterfall, Funnel, Box Plot and more, plus Ribbon, Gantt and Decomposition charts and offline country and US state maps.
- Named measures and calculated fields, Reports with filters, slicers, pivot tables and drill-through.
- Result profiles and explained findings that show how each number was calculated.

What it does not do yet: MySQL, BigQuery and Snowflake are coming soon, and shared browser publishing is not there yet. More databases and chart types are on the way.

Website: https://rockxy.io/rockxybase
Bug report and feature request: https://github.com/RockxyApp/RockxyBase

Hope it supports you guys working on Supabase and would love to hear your feedback!


r/Supabase • • 8d ago

storage Storage problem.

Thumbnail reddit.com
0 Upvotes

r/Supabase • • 8d ago

tips I built two free read-only checks for the Supabase holes AI app builders keep shipping (tested on a real project)

1 Upvotes

AI builders like Lovable and Bolt get you to a working Supabase app fast, but two things keep showing up: tables with RLS off or with using (true) policies, and secret keys (OpenAI, Stripe, even service_role) shipped in the frontend bundle.

In March 2025 a researcher found 170 of 1,645 Lovable showcase apps exposing user data this way: https://mattpalmer.io/posts/2025/05/statement-on-CVE-2025-48757/

So I put together two checks, both read-only:

  1. find-rls-holes.sql: paste into the SQL Editor. It lists tables with RLS off, policies open to everyone, policies open to any signed-in user (where auth.role() = 'authenticated' or auth.uid() is not null is the whole condition), views without security_invoker, and materialized views in public. It skips extension tables like PostGIS's.

  2. key-scanner.js: paste into the browser console on your live app. It looks for secret keys in the JS your site actually loaded, masks them in the output, and sends nothing anywhere.

I tested both on a throwaway Supabase project with deliberately bad policies before posting. The README says exactly what I tested and what the checks can't see.

https://github.com/faheemsaleem/supabase-leak-check

MIT licensed. If the SQL flags something on your project that you think is a false positive, tell me. I'd rather fix the query than have people trust it blindly.


r/Supabase • • 9d ago

database I scanned 100 public Lovable/Bolt apps for Supabase security mistakes. 7 of the 23 with migrations had tables anyone could edit.

2 Upvotes

I've been building with Supabase and kept running into the same few mistakes in AI-generated code, so I wrote a scanner for them and ran it on 100 public Lovable and Bolt projects on GitHub.

What it found, among the 23 apps that keep migrations in the repo:

  • 7 had at least one table that anyone, or any logged-in user, could change or delete. The most common pattern is a policy the AI names "System can manage X" with for all using (true). The AI means "only my backend", but without to service_role it applies to everyone.

  • 4 of the 100 had committed their service_role key. Two were in a committed .env file, one in a one-off migration script, and one in a docs file.

  • Several views were missing security_invoker = true, so they bypass RLS on the tables underneath.

Caveats: these are public repos, so mostly side projects, and a static scan can't see anything changed in the dashboard. I'm not naming any apps.

The scanner is free and open source and runs locally (your code isn't uploaded anywhere):

npx shipwarden

It replays your migrations in order, including DO $$ blocks and loops that enable RLS, so it doesn't flag tables you protected later. It decodes JWTs, so your public anon key never triggers an alarm. It's also a GitHub Action if you want it on every PR.

Repo: https://github.com/patrickballard/shipwarden

I'd really like to hear about false positives. If it flags something that's actually fine, tell me and I'll fix the rule.

Update: someone ran it on their production multi-tenant Next.js + Supabase app and got 16 false positives (auth in helper functions, signed webhooks, views closed to anon, and so on). All 7 patterns are fixed in 0.2.3, and views that filter by auth.uid() are now a low “check this” item instead of an alarm. If it’s noisy on your app, please open an issue. That’s exactly what makes it better.


r/Supabase • • 9d ago

tips A checklist for a Supabase incident packet, plus a local evidence tool

1 Upvotes

Disclosure: I own and sell the optional tool mentioned below. This post was drafted and submitted with AI assistance at my request. It is not affiliated with Supabase.

A useful incident packet should make it possible to distinguish what was observed from what is still a guess. Here is a checklist you can use without buying a tool:

  1. Keep a timeline with the original timestamp, timezone, and source for each observation. If you normalize to UTC, retain the original time as well.

  2. Separate billing observations, project pause/restore state, service health, DNS results, and application errors. A note about one does not establish the state of all the others.

  3. Record the time of each status check. Two observations from different times may describe a change rather than a contradiction.

  4. List attempted actions and their observed results. Keep hypotheses separate from supplied evidence, and explicitly mark missing information.

  5. Write the impact and the questions you need answered. Redact credentials, tokens, personal information, and private identifiers before sharing anything; review the final packet yourself.

For people who prefer a local template-driven workflow, I sell Supabase Recovery Evidence Agent. It takes an already-redacted incident JSON bundle and generates output/report.json and output/escalation.md, with a timeline, source references, documented contradiction findings, and missing-evidence checks.

It requires Python 3.10+, uses no third-party packages, and runs locally. It does not log into Supabase, make network calls, repair infrastructure, determine a definitive root cause, or contact support. Secret-pattern checks are only an aid and do not replace redaction.

The included fictional sample and exact first-run command are documented here: https://gptmarketplus.com/guides/supabase-incident-evidence-packet

The optional toolkit is a one-time $1.00 USD through PayPal, or 1.00 USDC on Base: https://score.agentid.life/supabase-recovery?ref=reddit-supabase-20261108

No recovery outcome or customer result is being claimed. For an actual account or billing issue, use Supabase's official support channel; this community post is a preparation checklist.