01 · How to use it
How do you use this code audit checklist?
Use it as a self-check first and as a yardstick for an outside code audit second.
- 01
Mark each check pass, fail or unknown, and keep a link to the evidence, such as a file, a pipeline run or a scan report.
- 02
Unknown is a result. Three or more unknowns in one area is a reason to bring in an independent reviewer. Our guide to choosing a code audit company covers what to ask them. The 40 checks are Ace8's working list, not an industry standard.
02 · Area 1
What should you check in the architecture?
Check whether the structure still matches the business, and whether one change can be made without touching ten files.
| # | Check | What to look for |
|---|---|---|
| 1 | Module boundaries | Clear packages or services, with few imports that cross them |
| 2 | Business rules | Rules live in one place, not copied into screens, queries and scripts |
| 3 | Circular dependencies | No cycles between modules, or a short list of known ones |
| 4 | Dead code | Unused classes, endpoints and feature flags identified |
| 5 | Written design | A diagram or note a new engineer could follow, even if dated |
03 · Area 2
What should you check in the tests?
Check whether the tests would catch a break in the parts of the system that matter most.
| # | Check | What to look for |
|---|---|---|
| 6 | Tests run | One command runs the suite, and it passes on a clean checkout |
| 7 | Critical paths | Sign-in, payments and core calculations have tests |
| 8 | Assertion quality | Tests assert results, not just that code ran without an error |
| 9 | Flaky tests | Failures are not routinely re-run until green |
| 10 | Test data | Fixtures do not depend on a shared live database |
04 · Area 3
What should you check in dependencies and CVEs?
Check that you know every component you ship and whether any carries a known vulnerability. OWASP lists not knowing component versions, including nested ones, and not scanning regularly as signs of exposure (checked 17 Nov 2026).
| # | Check | What to look for |
|---|---|---|
| 11 | Inventory | A lockfile or bill of materials lists direct and nested components |
| 12 | Known vulnerabilities | A scan has run, and critical findings have an owner |
| 13 | Age | Frameworks and runtimes still receive fixes from their maintainers |
| 14 | Unused packages | Dependencies nothing imports have been removed |
| 15 | Sources | Packages come from official registries, not a copied tarball or an unknown fork |
05 · Area 4
What should you check for security basics?
Check the obvious holes first: secrets in the repository, unchecked input and weak access rules. The OWASP Secrets Management Cheat Sheet says a secret found in code should be revoked, rotated and removed (checked 17 Nov 2026).
| # | Check | What to look for |
|---|---|---|
| 16 | Secrets in code | No keys, passwords or tokens in files or git history |
| 17 | Input handling | Queries are parameterized, and user input is validated before use |
| 18 | Authentication | Passwords are hashed with a modern algorithm; sessions expire |
| 19 | Authorization | Every endpoint checks who is asking, not only that someone is signed in |
| 20 | Error output | Stack traces and internal details are not shown to users |
06 · Area 5
What should you check in data access?
Check how code reads and writes data, since the data layer is often where a move or an upgrade gets stuck.
| # | Check | What to look for |
|---|---|---|
| 21 | Schema ownership | One component owns each table, and others go through it |
| 22 | Migrations | Schema changes are scripted and repeatable, not typed into production |
| 23 | Vendor-specific SQL | Database-specific features are listed, with a reason for each |
| 24 | Query load | Slow queries and loops that call the database per row are found |
| 25 | Backups and restore | A restore has been tested, not only a backup taken |
07 · Area 6
What should you check in build and deploy?
Check whether a new engineer could build and release the system on the first day without help from someone who has left.
| # | Check | What to look for |
|---|---|---|
| 26 | Reproducible build | A clean machine builds the same artifact from the repository |
| 27 | Automated pipeline | Tests run on every change before it merges |
| 28 | Configuration | Settings per environment live outside the code |
| 29 | Rollback | A bad release can be reversed, and someone has tried it |
| 30 | Environment parity | Staging resembles production closely enough to trust |
08 · Area 7
What should you check for licences?
Check which licences the code carries and whether they match how you distribute it.
| # | Check | What to look for |
|---|---|---|
| 31 | Open-source list | Every library and its licence is listed |
| 32 | Copyleft | Strong copyleft licences are identified and checked against how you ship |
| 33 | Copied code | Snippets pasted from the web or from AI tools are flagged |
| 34 | Commercial components | Paid libraries have a licence you can find and a seat count that matches use |
| 35 | Ownership | Contracts show who owns code written by outside developers |
09 · Area 8
What should you check for AI readiness?
Check whether the code could take AI features safely, and whether code written with AI tools has been reviewed. The AI readiness checklist covers the organization-wide view; these five cover the code.
| # | Check | What to look for |
|---|---|---|
| 36 | Reachable APIs | Core functions are exposed through stable interfaces, not only screens |
| 37 | Data reachability | Data an AI feature would need can be read without breaking access rules |
| 38 | Generated code marked | You know which parts were written with AI tools |
| 39 | Generated code reviewed | Tests, secrets and dependencies in that code were checked by a person |
| 40 | Outbound calls | Code that sends data to an outside AI service is listed and controlled |
10 · Next step
What do you do with the results?
Fix the failed checks in the security and dependencies areas first, then tests, since tests make the rest safer to change.
- 01
For checks you marked unknown, or an area with several fails, an independent code audit turns the list into a ranked report. Request a code audit quote and we will agree a fixed price after a short call.