2 env variables are missing from .env.example: NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY_LIVE, STRIPE_SECRET_KEY_LIVE.
Show evidence (2)
↳ NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY_LIVE → missing from committed env template
↳ STRIPE_SECRET_KEY_LIVE → missing from committed env template
Suggested fix: Document NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY_LIVE= + STRIPE_SECRET_KEY_LIVE= in .env.example and verify the values in Vercel. Repository files cannot prove whether hosting variables are set.
5 tables have no Data API grants in the migrations and will answer 42501 once the automatic grants are gone.
Why it works locally: Locally you only test as yourself. In production every visitor holds the public anon key, and server code shares one process across all of them, so only server-only keys and row level security protect your data.
Show evidence (5)
↳ supabase/migrations/20230530034630_init.sql:5 → public.users is created without a GRANT to anon, authenticated or service_role; Supabase is removing the automatic grants on new tables, and where that default applies the Data API answers 42501 permission denied
↳ supabase/migrations/20230530034630_init.sql:38 → public.customers is created without a GRANT to anon, authenticated or service_role; Supabase is removing the automatic grants on new tables, and where that default applies the Data API answers 42501 permission denied
↳ supabase/migrations/20230530034630_init.sql:51 → public.products is created without a GRANT to anon, authenticated or service_role; Supabase is removing the automatic grants on new tables, and where that default applies the Data API answers 42501 permission denied
↳ supabase/migrations/20230530034630_init.sql:74 → public.prices is created without a GRANT to anon, authenticated or service_role; Supabase is removing the automatic grants on new tables, and where that default applies the Data API answers 42501 permission denied
↳ supabase/migrations/20230530034630_init.sql:106 → public.subscriptions is created without a GRANT to anon, authenticated or service_role; Supabase is removing the automatic grants on new tables, and where that default applies the Data API answers 42501 permission denied
Suggested fix: Add a migration that grants only what each role needs, for example:
grant select on table public.users to anon;
grant select, insert, update, delete on table public.users to authenticated;
grant select, insert, update, delete on table public.users to service_role;
Keep row level security on: grants decide which roles reach the table, policies decide which rows.
A 24-hour pass for public and private repository scans. Private code requires your GitHub authorization. One-time payment, no subscription, nothing renews.
One link follows the latest public scan of the default branch, with its date and commit. Views never start scans.
Open repo status →[](https://deploydoctor.nyttolabs.com/score/vercel/nextjs-subscription-payments)
Scan button for your README
For templates and starters. The link points at this repository, so someone who forks it changes the owner/repo in the link to scan their own copy before the first deploy.
[](https://deploydoctor.nyttolabs.com/vercel/nextjs-subscription-payments)