What a builder's own check reads, and what a code audit reads
An app builder's security check runs inside the builder, on the project it holds. A code audit reads the code itself, in the saved version you hand over. Here the two sit side by side, so you can choose what your launch needs.
Two kinds of check
| Kind | What it reads | What it does not read |
|---|---|---|
| A builder's own security check | The project inside the builder's own tools. What it reads is set by the builder and stated on the builder's own page. | Whatever the builder's page does not list. That page sets its scope. |
| Nordik Audit, a code audit |
|
The running app, live database settings, hosting and third-party accounts. The code is read and never run. The audit can miss problems, and a finding can be wrong. The full limits are in the terms. |
Nordik App Audit supports every platform, including apps built with Lovable, Cursor or Claude Code, and hand-written code. Nordik is not affiliated with these tools.
What a named builder check says it checks, retrieved 2026-10-20
The row quotes the builder's own documentation, word for word, on the date shown. Nordik has not measured this check, and this table makes no claim about how well it works. The same page also describes a Deep scan.
| Product | What its own page says it checks | Source | Retrieved |
|---|---|---|---|
| Lovable Project security view | "Checks your code and your live database configuration for common security issues and known misconfigurations" | Lovable documentation, Project security view page | 2026-10-20 |