Ace8 is the modernization practice of AceMQ.24/7 support from AceMQ after go-live
Book an Assessment

Stacks we work in

  • Java
  • Spring Boot
  • Kubernetes
  • PostgreSQL
  • Kafka
  • Docker
  • Terraform
  • GitHub Actions
  • Java
  • Spring Boot
  • Kubernetes
  • PostgreSQL
  • Kafka
  • Docker
  • Terraform
  • GitHub Actions
The short answer

A code audit checklist covers eight areas: architecture, tests, dependencies and CVEs, security basics, data access, build and deploy, licences, and AI readiness. This one has five checks per area, 40 in total. For each check, write down the evidence you found. A check you cannot show evidence for counts as failed.

Next stepFixed-price assessmentInventory, risk score and a phased roadmap with a fixed price for phase one.Book a fixed-price assessment

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.

  1. 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.

  2. 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.

#CheckWhat to look for
1Module boundariesClear packages or services, with few imports that cross them
2Business rulesRules live in one place, not copied into screens, queries and scripts
3Circular dependenciesNo cycles between modules, or a short list of known ones
4Dead codeUnused classes, endpoints and feature flags identified
5Written designA 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.

#CheckWhat to look for
6Tests runOne command runs the suite, and it passes on a clean checkout
7Critical pathsSign-in, payments and core calculations have tests
8Assertion qualityTests assert results, not just that code ran without an error
9Flaky testsFailures are not routinely re-run until green
10Test dataFixtures 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).

#CheckWhat to look for
11InventoryA lockfile or bill of materials lists direct and nested components
12Known vulnerabilitiesA scan has run, and critical findings have an owner
13AgeFrameworks and runtimes still receive fixes from their maintainers
14Unused packagesDependencies nothing imports have been removed
15SourcesPackages 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).

#CheckWhat to look for
16Secrets in codeNo keys, passwords or tokens in files or git history
17Input handlingQueries are parameterized, and user input is validated before use
18AuthenticationPasswords are hashed with a modern algorithm; sessions expire
19AuthorizationEvery endpoint checks who is asking, not only that someone is signed in
20Error outputStack 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.

#CheckWhat to look for
21Schema ownershipOne component owns each table, and others go through it
22MigrationsSchema changes are scripted and repeatable, not typed into production
23Vendor-specific SQLDatabase-specific features are listed, with a reason for each
24Query loadSlow queries and loops that call the database per row are found
25Backups and restoreA 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.

#CheckWhat to look for
26Reproducible buildA clean machine builds the same artifact from the repository
27Automated pipelineTests run on every change before it merges
28ConfigurationSettings per environment live outside the code
29RollbackA bad release can be reversed, and someone has tried it
30Environment parityStaging 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.

#CheckWhat to look for
31Open-source listEvery library and its licence is listed
32CopyleftStrong copyleft licences are identified and checked against how you ship
33Copied codeSnippets pasted from the web or from AI tools are flagged
34Commercial componentsPaid libraries have a licence you can find and a seat count that matches use
35OwnershipContracts 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.

#CheckWhat to look for
36Reachable APIsCore functions are exposed through stable interfaces, not only screens
37Data reachabilityData an AI feature would need can be read without breaking access rules
38Generated code markedYou know which parts were written with AI tools
39Generated code reviewedTests, secrets and dependencies in that code were checked by a person
40Outbound callsCode 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.

  1. 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.

FAQ

Frequently asked questions

Short answers to what buyers ask first. Something else on your mind? Ask an engineer.

A list of checks an auditor runs on a codebase: structure, tests, dependencies, security basics, data access, build and deploy, licences and AI readiness.

Start here

Know the cost before anything moves.

A fixed-price assessment gives you the inventory, the risk score and a phased plan. Scope and cost are fixed before the migration starts.

Inventory
Every application, its stack and what it depends on.
Risk score
Where a change is likely to break, ranked.
Phased plan
What moves first, which tools lead, and the fixed price.

Get in touch

Talk to a modernization engineer.

Tell us what you run today. An engineer, not a sales script, replies within one business day.

305-204-2607info@ace8.io

66 W. Flagler St. 9th Floor
Miami, FL 33130

What are you moving off? *

Fixed price. Scope and cost before any migration starts.