03.03Run

Code audits

Code audits from Hot Rocket Software, a team of software, website and digital marketing specialists based in the UK, with 19 years in IT. An independent review of a codebase: security, architecture, maintainability and hosting risks, written up in plain English with a prioritised fix list.

UPTIME · DEPLOYS · BACKUPS03.03 CODE AUDITS

03.03.0

What is code audits?

A code audit is an independent read of your software by senior engineers: how secure it is, how maintainable, how it is hosted and what it would take to change it. You get a plain-English report with a prioritised list of fixes. It is useful before taking over a project, buying a business or deciding whether to rebuild.

See where code audits fits in our work →

03.03.1

Who is it for?

  • Businesses inheriting software from a previous supplier
  • Investors or buyers doing technical due diligence
  • Teams deciding between refactoring and rebuilding

03.03.2

From a small business to a large organisation

The same team takes on a single tool for a small business and long-running work for large companies and the public sector. Here is what each end looks like.

For a small business

A plain-English report on the state of the software you rely on, and what to fix first.

For large companies and the public sector

Independent reviews of large codebases before procurement, a supplier change or a major investment.

  • Pre-procurement technical due diligence
  • Supplier exit and takeover reviews
  • Security and accessibility audits
  • Modernisation plans

How we work with enterprise and the public sector →

03.03.3

What you get

  1. 01Security review including dependencies and secrets handling
  2. 02Architecture and code quality assessment
  3. 03Hosting, backup and deployment review
  4. 04A prioritised fix list with rough effort
  5. 05A walkthrough call to go through findings

03.03.4

How we approach it

  1. Access

    Read-only access to code, hosting and documentation.

  2. Review

    Automated scans plus a manual read by a senior engineer.

  3. Report

    Plain-English findings, ranked by risk.

  4. Walkthrough

    A call to answer questions.

  5. Optional

    Help to fix, or a support plan.

03.03.5

Questions

How long does a code audit take?

It depends on the size of the codebase. We agree a fixed scope and price after a first look.

Do you need write access?

No. Read-only access is enough, and we sign an NDA if you need one.

Will you just tell us to rebuild?

Rarely. Most codebases are worth fixing. The report says which parts, and which are not.

T+99Next step

Talk it through with us

A free 30-minute first chat, with no obligation. Tell us what is getting in the way; we tell you honestly what we would do, roughly what it would take, and whether it is worth doing at all.