Bolt app security audit

Bolt apps most often go wrong in three places: who can read and change data, secret passwords (called keys) that end up where every visitor can copy them, and prices or limits that a visitor can change before sending them. A Bolt app security audit reads your code and your data rules and gives you a Bolt prompt for each fix.

Report in 48 hours or you're not charged. Your card is only held until the report is delivered.

Start with the free scan

  1. Open scan.getnordik.com and paste the link to your app.
  2. Press "Scan my app". There is no sign-up, and nothing to place on your app.
  3. Get hints in under a minute about what your app shows to the outside. The scan opens only what any visitor's device opens; it never signs in or writes anything.

What the $129 audit gives you

  • A plain-words report that says what each problem means for your users, and how serious it is, without security jargon.
  • A technical report with the file and line of every finding, for you or a developer.
  • A copy-paste fix prompt for every finding. Each fix prompt is written for Bolt: one change per prompt, naming the table or function and the exact rule wanted. Where we could check a fix, you get the checked fix too.
  • A "how to check it is fixed" step for each finding, and a free re-check after you fix.
  • Money back if a confirmed finding is wrong.

The audit is AI-performed: it reads your code and the rules that guard your data, and it is not a penetration test.

Every audit is read by the owner before it reaches you.

The free scan works for every platform. Its hints point at where to look; the audit reads the code and confirms what is really there. For deeper checks you can show the app is yours with a one-time code. That step is optional.

What usually goes wrong in Bolt apps

Bolt usually builds a web app that keeps its data in a Bolt Cloud database, which runs on a service called Supabase, or in your own Supabase project. Small programs that run out of visitors' sight hold the secret passwords.

Data rules that let users see each other's data

The most important question in any Bolt app: can a user only reach their own data? A table of data with its protection switched off (Supabase calls it row-level security), or with a rule that is always true, answers "no".

Source: Bolt support: Security; Supabase documentation: Row Level Security

Prices and limits a visitor can change

If the page itself sends the price, the quantity or "this coupon is still valid", someone can change it on their own device before it reaches your app. Bolt's own documentation names this kind of misuse.

Source: Bolt support: Security

Secret passwords left where visitors can copy them

A key is a password your app uses to reach a paid service. It belongs in the hidden part of your app, never in the part every visitor downloads. Once a key has been out in the open, replace it: make a new one and turn the old one off, because it may already have been copied.

Source: Bolt support: Security; Vite documentation: Env variables and modes

Uploads and form input taken on trust

File uploads, links and text that visitors type should go through a check in the hidden part of your app, or they can carry content you did not expect into your app.

Source: Bolt support: Security; OWASP Authorization Cheat Sheet

Bolt's own security check

Bolt runs a security audit when you publish and can fix many issues itself; its documentation also says some changes need you, for example in connected payment or email services. The Nordik audit is an independent read on top: a report you can read in one sitting, with a fix prompt and a "how to check it is fixed" step for every finding.

Source: Bolt blog: Security audit on publish; Bolt support: Security

How ordering works

  1. Send your Bolt project to GitHub, a website that stores code. Bolt can create the folder that holds your code there (a repository). Share it with us, or download the project and send it.
  2. Check out for $129. Your card is held, not charged.
  3. Your report arrives within 48 hours. The charge happens only then; if it does not arrive in time, you are not charged.

Order the $129 audit

Nordik App Audit supports every platform, and Bolt apps can order today.

A stack is the set of tools an app is built on. Before a report goes out, our checks for a stack must pass our own quality test. A stack that has passed is called qualified; for a stack not qualified yet, that work is done after you order.

We support every platform. Bolt apps usually run on React/Vite + Supabase. Bolt apps and any other stack are qualified on demand inside the same 48 hours, and if we cannot deliver a passing report in time, your hold is released and you pay nothing.

Qualification is per family. Next.js + Supabase: the newest re-check passed config headers errors (a measurement, not yet a promise); not yet measured after the newest re-check: route authorization, service role, object scoping, request trust, database policy, secrets (we still look there, but a clean result in them is not a pass).

Recall was met in route authorization, database policy, secrets, but high and critical findings from that run are still unchecked against a label, so we do not call them qualified. Today we do not promise any part of this stack as fully checked. Every report is held to the same quality check before it reaches you.

Questions

How do I do a security audit of a Bolt app?

Run Bolt's own audit first, then get an independent read. Start with the free scan of your app's public link; for the full picture, the $129 audit reads your code and data rules and gives you a Bolt prompt for each fix.

What security issues do Bolt apps usually have?

Data rules that let one user reach another user's data, prices or limits a visitor can change on their own device, secret passwords (keys) in the part of the app every visitor downloads, and form or upload input that nothing checks once it arrives.

What does the free scan of a Bolt app look at?

Only what your app already shows to anyone on the internet. You paste the link to your app and press one button, and in under a minute the scan gives you hints about what may be in public view by mistake. Showing the app is yours with a one-time code is optional and adds deeper checks. The scan never signs in, writes or submits anything, and it does not read your code. Hints are not findings: the audit reads the code to confirm them.

What do I get for $129?

A plain-words report and a technical report, a copy-paste fix prompt and a "how to check it is fixed" step for every finding, plus a free re-check after you fix. If a confirmed finding turns out to be wrong, you get your money back. It is a one-time price, not a subscription.

How fast is the report, and when am I charged?

Report in 48 hours or you are not charged. At checkout your card is only held; the charge happens when the report is delivered. Nordik App Audit supports every platform, and Bolt apps can order today. A stack is the set of tools an app is built on. Before a report goes out, our checks for a stack must pass our own quality test. A stack that has passed is called qualified; for a stack not qualified yet, that work is done after you order. We support every platform. Bolt apps usually run on React/Vite + Supabase. Bolt apps and any other stack are qualified on demand inside the same 48 hours, and if we cannot deliver a passing report in time, your hold is released and you pay nothing. What our own testing has measured so far is set out under "How ordering works" on this page.

Is this a penetration test?

No. It is not a penetration test, which tries, with your permission, to break into your running app. Nordik App Audit is an AI-performed audit: it reads your code and the rules that guard your data, and never attacks your app. Like any review it can miss things, which is why every finding comes with a way to check the fix yourself.

Sources

Nordik is not affiliated with Bolt. Product names belong to their owners.