Contents
A code audit reviews an application’s source code to judge its quality, security and maintainability: structure, technical debt, dependencies, tests, documentation and how easily it can be taken over. It answers a simple question: can this application evolve safely, and at what cost? It is part of my full audit at $2,200 (€1,990)excl. VAT.
A web application can work perfectly for its users and still be impossible to evolve. This is common when the original provider is gone, when development was rushed, or when the app was generated with an AI tool. A code audit tells you before you commit a budget, not after.
The questions the audit answers
- Can another developer take over this code without breaking everything?
- Are the dependencies maintained, or does the app rely on abandoned libraries?
- What will a new feature cost compared with a healthy application?
- Should it be fixed, partly rewritten or rebuilt from scratch?
What gets reviewed
| Area | What I look at | Warning sign |
|---|---|---|
| Structure | Folder organization, separation of concerns | One file of several thousand lines that does everything |
| Readability | Naming, consistency, duplication | The same calculation copied in several places, with differences |
| Dependencies | Versions, maintenance, known vulnerabilities | Libraries with no update for years |
| Data | Database structure, migrations, integrity | Duplicated data, no history of schema changes |
| Security | Server-side permission checks, secrets, injections | API keys in the code or in the browser |
| Tests | Presence, coverage of critical parts | No tests on money or stock calculations |
| Deployment | Repeatable process, separate environments | Production releases done by hand on the server |
| Documentation | Setup, architecture, decisions | Only the person who left knew how it works |
For security, I rely on the OWASP Top 10 (2025 edition, accessed November 17, 2026). The security checks are detailed in the web application security audit.
Fix or rewrite: the decision grid
| Audit finding | Usual recommendation |
|---|---|
| Readable code, a few outdated dependencies, few tests | Fix, and add tests on the critical parts |
| Good database, disorganized code | Keep the data and rewrite the code gradually, module by module |
| Structural security flaws, permissions handled in the browser | Rewrite the affected layer before any production launch |
| Inconsistent code and data, no documentation, abandoned technology | Rewrite, carrying over the existing data |
A full rewrite is rarely the best answer. It makes sense when fixing would cost more than rebuilding, over three years and not just next month. The pages taking over an app built with Lovable and taking over an app built with Bolt or Cursor cover common cases.
How the audit works
- A 30-minute call: what the application does, why you want it audited, what decision you have to make.
- Access to the code: a Git repository or an archive, ideally with read access to the database and hosting.
- The analysis: automated tools (dependencies, quality), then a manual review of the critical parts.
- The report: findings ranked by severity, estimated fixes, a clear recommendation.
- A 2-hour debrief to answer your questions and your team’s.
The code audit is part of the full audit at $2,200 (€1,990)excl. VAT (5 to 7 days, six areas, costed action plan, 30 days of support). The express audit at $650 (€589)excl. VAT gives a faster first read.
Before signing with a new provider
A code audit by a third party also protects the next relationship: the new provider starts from a shared assessment instead of discovering problems invoice after invoice. It is also the basis of an audit before acquiring a company, covered in technical due diligence on software.
Frequently asked questions
What is the difference between a code audit and a security audit?
A security audit looks for exploitable flaws. A code audit also judges whether the application can last: readability, organization, tests, dependencies, documentation. An application can be secure today and very expensive to evolve tomorrow.
Do I need the former provider’s agreement?
Above all, you need the code and the right to use it. Check your contract: if ownership of the code was transferred to you, you can have it audited freely. If you have no access to the repository, that is the first thing to fix, before the audit itself.
Can the audit cover an app generated with Lovable, Bolt or Cursor?
Yes. These apps often work well in a demo but show recurring weaknesses: permissions checked only in the browser, exposed keys, no tests. The audit finds them and estimates the cost of fixing them.
What if the audit concludes that everything must be rewritten?
The report explains and justifies it, with an estimate. A rewrite is only recommended if fixing would cost more over time. Often the right answer is in between: keep the database and rewrite part of the code.