SAMPLE Sample report. Built from InvoicePond, an invented v0-style app written by Nordik Audit with planted problems. Not a customer and not a real company. A limited audit, not a full one, as the report says under "What we checked, and who checked it".

App Audit report: v0-invoicepond

Built and run by Nordik, an independent application security audit service.

What to fix first

How bad is it? Serious. Someone could get a private key your app marks as safe to share, read or change other people's data without signing in, or read or change any of your data through your database admin key.

What to do first: 9 things are marked Fix today. If real people use your app now, start with these 5 and then fix the rest of them today too. If you cannot fix all 9 today, pause the app until you can. If it is not live yet, fix them before you launch. Once item 1 is done, make a new key and turn off the old one, because the old one may already have been copied. Item 1 shows how, step by step.

  1. A private key is marked as safe to send to browsers (item 1)
  2. Your database admin key is used with no sign-in check (item 2)
  3. Your database admin key is used with no sign-in check (item 3)
  4. Your database admin key is used in the wrong place (item 4)
  5. The shared sign-in check leaves some of your app open (item 5)

All of it: 13 things to fix below, worst first for your users' data and money: 9 to fix today, 1 to fix this week and 3 worth a look. Item 13 updates all your old packages with one prompt. Package updates come last even when marked Fix this week: the warning about them is public, but we did not check whether your app uses the weak part.

How to use each item: Paste its fix prompt into v0's chat. Then open "Show me how to check / step by step" under it for the check (v0 answers Pass or Fail) and any steps you do yourself. Each item says how long it usually takes: a rough guess from the kind of fix, not a promise.

Has anyone done this yet? This report cannot tell. Your app's visit records (logs) can.

Show me how to check / step by step

Where to look: in Vercel (where v0 puts your app live), open your project, then Logs; in Supabase, open your project, then Logs in the left menu. If they are hard to read, paste this into v0's chat and v0 walks you through them:

A security audit found problems in my app that could let strangers reach other people's data. Help me check whether anyone has done this already. Do not change anything. Tell me step by step, button by button, how to open my app's visit records (logs) in Vercel and Supabase for the last 30 days, and what to look for, in plain words. Then tell me what you found, if you can see them.
Fix today 1. A private key is marked as safe to send to browsers
  • What this means for you: This key's name tells your app it is safe to send to visitors' browsers. Any page that uses it would hand it to every visitor, who could copy it. A key like this should only be used on your server.
  • How urgent: Fix today
  • How long it takes: usually about 30 minutes (a code change, a new key at the service, then the check)

Fix prompt: Paste this into v0's chat as-is. You don't need to understand it.

A security audit of my v0 app found a problem. Please fix it. In `lib/supabase/admin.ts` (around line 5) a private key is in a setting whose name makes it public, so it is sent to every visitor's browser. Rename the setting so only the server can read it, use the key only in code that runs on the server, and keep only the public key where the browser needs one. Any server code that uses the key must first check that the caller is signed in and allowed (for an admin action, a role stored in the database, never in user_metadata), and touch only the rows that caller may change. Change only what moving the key needs: do not rewrite other features, pages or database rules. Delete the key value from the committed file (keep the name with an empty value if the code reads it), and never put a private key under a name that starts with VITE_ or NEXT_PUBLIC_. Then remind me to make a new key and turn off the old one, since the old one may have been copied. Any error you send back must be a short general message, never the raw error text. Do not add a SECURITY DEFINER database function. A database rule you add must not let users change status, role, payment or owner fields, or link a row to data of another user. Keep everything else working the same. Then tell me in plain words what you changed.
Show me how to check / step by step
  • How to check it's fixed: Paste this into v0's chat after the fix:
Check the fix you just made for: a private key is marked as safe to send to browsers. Search the code that runs in visitors' browsers for the private key the audit found in `lib/supabase/admin.ts` (around line 5). Tell me if any page could still send that key to a visitor, without showing the key. Change nothing. Answer Pass or Fail, with one plain sentence why.
  • Your own step: make a new key once the fix is in (the old one may have been copied).
    1. In your Supabase dashboard, open your project, then Settings, then API Keys. Add a new secret key and copy it.
    2. Paste the prompt below into v0's chat. v0 tells you what to name the new key.
    3. Add the new key under that name in v0: open the project menu (the ... button), then Settings, then Environment Variables. Never paste a key into the chat.
    4. When v0 says the app runs on the new key, turn the old key off on Supabase's API Keys page.
I am making a new Supabase secret key to replace the private key a security audit found in my app. I will add it to the project's secret settings myself, so never ask me to paste it here. Tell me the exact name to give it, and make the app read it only in code that runs on the server. If the app still uses Supabase's old public key, move it to a new publishable key too, so I can turn off the old keys. When I say it is done, check that the app still runs, and tell me when I can turn the old key off.
  • Details for a developer: C001 in the technical report
Fix today 2. Your database admin key is used with no sign-in check
  • What this means for you: This part of your app uses the admin key to your database, which can read and change everything, and it does not check who is asking. Someone who finds it could read or change data that is not theirs, without signing in.
  • How urgent: Fix today
  • How long it takes: usually about 15 minutes (a code change in one file, then the check)

Fix prompt: Paste this into v0's chat as-is. You don't need to understand it.

A security audit of my v0 app found a problem. Please fix it. In `app/api/invoices/[id]/route.ts` (around line 8) the code uses the Supabase admin key (the service role key), which skips every database rule, to answer requests from visitors. Change this code to use the normal Supabase client with the signed-in user's session, so the database rules apply. If the code does not check who is signed in, add that check first and turn away anyone who is not allowed. Keep the admin key only for trusted jobs on the server. Also scope every read and write here to the signed-in owner (user_id = auth.uid() or the equivalent), both in the database rules (RLS) and in the server query. An owner may change only the fields they should edit, never status, role, payment or owner fields. Any linked row the request names (such as a client, a child or a booking) must belong to the signed-in owner too, in the database rules as well as in the code. Any error you send back must be a short general message, never the raw error text. Do not add a SECURITY DEFINER database function. A database rule you add must not let users change status, role, payment or owner fields, or link a row to data of another user. Keep everything else working the same. Then tell me in plain words what you changed.
Show me how to check / step by step
  • How to check it's fixed: Paste this into v0's chat after the fix:
Check the fix you just made for: your database admin key is used with no sign-in check. For `app/api/invoices/[id]/route.ts` (around line 8), tell me whether someone who is not signed in could still get data back, and whether that code still uses the database admin key to answer visitors. Change nothing. Answer Pass or Fail, with one plain sentence why.
  • Details for a developer: C002 in the technical report
Fix today 3. Your database admin key is used with no sign-in check
  • What this means for you: This part of your app uses the admin key to your database, which can read and change everything, and it does not check who is asking. Someone who finds it could read or change data that is not theirs, without signing in.
  • How urgent: Fix today
  • How long it takes: usually about 15 minutes (a code change in one file, then the check)

Fix prompt: Paste this into v0's chat as-is. You don't need to understand it.

A security audit of my v0 app found a problem. Please fix it. In `app/api/invoices/route.ts` (around line 24) the code uses the Supabase admin key (the service role key), which skips every database rule, to answer requests from visitors. Change this code to use the normal Supabase client with the signed-in user's session, so the database rules apply. If the code does not check who is signed in, add that check first and turn away anyone who is not allowed. Keep the admin key only for trusted jobs on the server. Also scope every read and write here to the signed-in owner (user_id = auth.uid() or the equivalent), both in the database rules (RLS) and in the server query. An owner may change only the fields they should edit, never status, role, payment or owner fields. Any linked row the request names (such as a client, a child or a booking) must belong to the signed-in owner too, in the database rules as well as in the code. Any error you send back must be a short general message, never the raw error text. Do not add a SECURITY DEFINER database function. A database rule you add must not let users change status, role, payment or owner fields, or link a row to data of another user. Keep everything else working the same. Then tell me in plain words what you changed.
Show me how to check / step by step
  • How to check it's fixed: Paste this into v0's chat after the fix:
Check the fix you just made for: your database admin key is used with no sign-in check. For `app/api/invoices/route.ts` (around line 24), tell me whether someone who is not signed in could still get data back, and whether that code still uses the database admin key to answer visitors. Change nothing. Answer Pass or Fail, with one plain sentence why.
  • Details for a developer: C003 in the technical report
Fix today 4. Your database admin key is used in the wrong place
  • What this means for you: The admin key to your database can read and change everything, and it skips all of your database rules. Used in the wrong place, it lets anyone who reaches that part of your app read or change any of your data.
  • How urgent: Fix today
  • How long it takes: usually about 15 minutes (a code change in one file, then the check)

Fix prompt: Paste this into v0's chat as-is. You don't need to understand it.

A security audit of my v0 app found a problem. Please fix it. In `app/api/invoices/route.ts` (around line 6) the code uses the Supabase admin key (the service role key), which skips every database rule, to answer requests from visitors. Change this code to use the normal Supabase client with the signed-in user's session, so the database rules apply. If the code does not check who is signed in, add that check first and turn away anyone who is not allowed. Keep the admin key only for trusted jobs on the server. What the audit saw: in `app/api/invoices/route.ts` at line 6 the code reads: "user_id: z.string().uuid(),". Also scope every read and write here to the signed-in owner (user_id = auth.uid() or the equivalent), both in the database rules (RLS) and in the server query. An owner may change only the fields they should edit, never status, role, payment or owner fields. Any linked row the request names (such as a client, a child or a booking) must belong to the signed-in owner too, in the database rules as well as in the code. Any error you send back must be a short general message, never the raw error text. Do not add a SECURITY DEFINER database function. A database rule you add must not let users change status, role, payment or owner fields, or link a row to data of another user. Keep everything else working the same. Then tell me in plain words what you changed.
Show me how to check / step by step
  • How to check it's fixed: Paste this into v0's chat after the fix:
Check the fix you just made for: your database admin key is used in the wrong place. For `app/api/invoices/route.ts` (around line 6), tell me whether someone who is not signed in could still get data back, and whether that code still uses the database admin key to answer visitors. What the audit saw: in `app/api/invoices/route.ts` at line 6 the code reads: "user_id: z.string().uuid(),". Fail only if this flaw is still there at that code: your database admin key is used in the wrong place. That is the code the audit looked at, not the problem itself: a correct fix may leave that line as it is. Change nothing. Answer Pass or Fail, with one plain sentence why.
  • Details for a developer: C019 in the technical report
Fix today 5. The shared sign-in check leaves some of your app open
  • What this means for you: The shared sign-in check decides which pages and routes ask people to sign in. A part it does not cover can be used by someone who is not signed in.
  • How urgent: Fix today
  • How long it takes: usually about 15 minutes (a code change in one file, then the check)

Fix prompt: Paste this into v0's chat as-is. You don't need to understand it.

A security audit of my v0 app found a problem. Please fix it. In `lib/supabase/middleware.ts` (around line 28) the shared sign-in check (middleware) decides which pages and routes ask people to sign in. Change it so every page and every API route that should be private is covered, not only the page paths it covers now: someone who is not signed in must be sent to sign in (for a page) or get a short error (for an API route). Leave public pages as they are. What the audit saw: in `lib/supabase/middleware.ts` at line 28 the code reads: ` if (!user && request.nextUrl.pathname.startsWith("/dashboard")) { `. Keep everything else working the same. Then tell me in plain words what you changed.
Show me how to check / step by step
  • How to check it's fixed: Paste this into v0's chat after the fix:
Check the fix you just made for: the shared sign-in check leaves some of your app open. For `lib/supabase/middleware.ts` (around line 28), tell me which paths the shared sign-in check covers now. Tell me whether someone who is not signed in could still use an API route or page that should be private, without being turned away. What the audit saw: in `lib/supabase/middleware.ts` at line 28 the code reads: ` if (!user && request.nextUrl.pathname.startsWith("/dashboard")) { `. Fail only if this flaw is still there at that code: the shared sign-in check leaves some of your app open. That is the code the audit looked at, not the problem itself: a correct fix may leave that line as it is. Change nothing. Answer Pass or Fail, with one plain sentence why.
  • Details for a developer: C020 in the technical report
Fix today 6. Your database admin key is used with no sign-in check
  • What this means for you: This part of your app uses the admin key to your database, which can read and change everything, and it does not check who is asking. Someone who finds it could read or change data that is not theirs, without signing in.
  • How urgent: Fix today
  • How long it takes: usually about 15 minutes (a code change in one file, then the check)

Fix prompt: Paste this into v0's chat as-is. You don't need to understand it.

A security audit of my v0 app found a problem. Please fix it. In `app/dashboard/invoices/actions.ts` (around line 9) the code uses the Supabase admin key (the service role key), which skips every database rule, to answer requests from visitors. Change this code to use the normal Supabase client with the signed-in user's session, so the database rules apply. If the code does not check who is signed in, add that check first and turn away anyone who is not allowed. Keep the admin key only for trusted jobs on the server. Also scope every read and write here to the signed-in owner (user_id = auth.uid() or the equivalent), both in the database rules (RLS) and in the server query. An owner may change only the fields they should edit, never status, role, payment or owner fields. Any linked row the request names (such as a client, a child or a booking) must belong to the signed-in owner too, in the database rules as well as in the code. Any error you send back must be a short general message, never the raw error text. Do not add a SECURITY DEFINER database function. A database rule you add must not let users change status, role, payment or owner fields, or link a row to data of another user. Keep everything else working the same. Then tell me in plain words what you changed.
Show me how to check / step by step
  • How to check it's fixed: Paste this into v0's chat after the fix:
Check the fix you just made for: your database admin key is used with no sign-in check. For `app/dashboard/invoices/actions.ts` (around line 9), tell me whether someone who is not signed in could still get data back, and whether that code still uses the database admin key to answer visitors. Change nothing. Answer Pass or Fail, with one plain sentence why.
  • Details for a developer: C006 in the technical report

More things to fix (items 7 to 13). Each one has the same parts as the items above, with the same number: what it means, the fix prompt, how to check it and any steps you do yourself. They are in the technical report, under "Fix prompts for the other items". Paste a fix prompt the same way.

What we checked, and who checked it

Sample report on an invented app. Nordik Audit. Technical report.