Security code reviewUSD · EUR

Security code review.

A security code review is a read of your source code looking for the flaws an attacker would use: auth, secrets, injection, uploads and vulnerable dependencies. Mine is the 14-day Trial, $995, one time. I send findings ranked by risk in the first 5 business days, then fix what can be fixed in the 14 days. It ends with a written plan for the rest and a walkthrough call. It is a source review, not a penetration test.

By Badii Boutar · Updated

Illustration: an old iron padlock.

$995 14 days, one time
  • Read by hand, then checked with scanners
  • Every finding with a severity and a fix
  • Fixed price, published

Security code review

What I check.

  1. 01

    Auth and access

    Login, sessions, password reset, roles, and whether every endpoint checks who is asking.

  2. 02

    Secrets

    Keys and tokens in the code, in the git history, in the front-end bundle and in config files.

  3. 03

    Input and injection

    SQL and NoSQL queries, HTML output, redirects, and anything built from user input.

  4. 04

    File uploads

    Type and size checks on both the front end and the back end, where files are stored and who can read them.

  5. 05

    Dependencies

    Libraries with known vulnerabilities, abandoned packages, and framework versions that no longer get security updates.

  6. 06

    Encryption and data

    What is encrypted, where keys live, and what personal data ends up in logs.

Process

How it works.

  1. 01

    30 min

    Scope

    Repos, stack, and what data the app holds.

  2. 02

    Day 1

    Repo access

    An invite to the repo. No passwords, no production access needed.

  3. 03

    Days 1 to 5

    Review

    I read the risky parts by hand first, then run linters, dependency checks, scanners and SonarQube. Findings ranked by severity, each with where it is and how to fix it, arrive in the first 5 business days.

  4. 04

    To day 14

    Fixes and call

    I fix what can be fixed in the 14 days. Then a written plan for what is left and a call to go through it.

Proof

From my work.

The worst security issue I have found in someone else’s code was a file upload with no check on file type or size, neither on the front end nor on the back end. Anyone could upload anything, of any size. A scanner will not always flag that. Reading the upload flow end to end does.

At Mom Software, the architecture work removed insecure third-party libraries and hard-coded keys, and moved the app to an Angular version that still gets security updates.

At Guntrack I built end-to-end encryption for the web and mobile app, with the clients’ keys managed in Google Cloud KMS. The hardest part was the Cloud KMS integration, which was tricky to get right at the time.

When not to hire me for this

  • You need a penetration test of the running system, or a pentest report for a client or an auditor. Hire a pentest firm.
  • You need a compliance certificate such as SOC 2 or ISO 27001. This is an engineering review. I do not issue certificates.
  • Your app was built with Lovable, Bolt or a similar tool and it needs more fixing than fits in 14 days. A monthly plan does that, one task at a time.

Price · USD

Price.

  1. 01

    14-day Trial

    I audit one app, codebase, site, store or cloud account, then fix what can be fixed in the 14 days.

    Fee credited to your first month if you start a monthly plan within 14 days of the Trial ending.

    • Findings ranked by risk, in the first 5 business days
    • Fixes for what fits in the 14 days, at the Limited pace
    • A written plan for the rest, and 1 walkthrough call

    $995

    14 days, one time

    Start · $995

    Secure checkout via Stripe · Refund policy

Good to know
  • Monthly plans are billed from the day you start. Pause or cancel anytime before the next billing date.
  • One task is a piece of work that fits in 1 to 5 working days. I size tasks and split bigger ones.
  • Your queue is unlimited and you set the order. I work through it one task at a time.
  • Messages are answered the same working day, Monday to Friday. All code and accounts stay yours.
  • Not included: 24/7 emergency support, and your own tool bills (hosting, APIs, payment fees).
  • The 14-day Trial is paid upfront and runs at the Limited pace. Fee credited to your first month if you start a monthly plan within 14 days of the Trial ending.
  • The Trial does not renew. If you do not start a plan, it ends on day 14 and nothing else is charged.
  • Prices exclude VAT. EU businesses with a valid VAT number pay no VAT on the invoice (reverse charge). Invoices come from Pan African Center for Entrepreneurship in the Netherlands.
  • Founding rate: the first 3 clients get 20% off, in return for a named testimonial and a case study. On a monthly plan, the 20% applies to the first month.
  • All three prices, and what each plan covers

Market

Where my price sits.

Published security code review prices, read again in November 2026. US fixed fees for source review are rarely published.

  • White-box testing in the UK: £5,000 to £35,000+ a project, on average £8,000 to £20,000, at £1,200 to £1,600 a day. Vendor guide. Source: Cyphere (UK), 7 Apr 2026
  • A basic security review for apps under 10,000 lines: $1,500 to $4,000 (InApps Technology, quoted second-hand). Source: AxonBuild, 24 Aug 2026
  • A $500 quick security check, or a $1,500 audit with a written report, fixes not included (vibecoding.app, quoted second-hand). Source: AxonBuild, 24 Aug 2026

At $995 for one codebase, the Trial sits under the UK white-box averages, under the basic review range, and between the $500 quick check and the $1,500 audit. The second-hand figures are less reliable than the Cyphere guide. I sell this, so read it with that in mind.

FAQ

Questions.

Illustration: a statue of a seated man, deep in thought.

01 What is the difference between a security code review and a pentest?

A security code review reads the source and finds flaws where they are written. A penetration test attacks the running app from outside, without the code. The review finds problems a pentest can miss, such as a key in the git history, and tells you the line to fix. It does not test your servers, network or cloud setup.

02 Which tools do you use?

Linters, dependency checks, security scanners and SonarQube. The tools catch the known patterns, and they never get bored on line 4,000. Reading by hand catches the logic flaws they miss.

03 Can you fix what you find?

Yes. The Trial includes fixing what can be fixed in the 14 days. The rest goes on a monthly plan, Limited at $1,995 or Full at $4,995, one task at a time. You can also hand the written plan to your own team.

04 Do you sign an NDA?

Yes. Confidentiality is already in my terms, and I sign your NDA on request before getting access.

Terms of service

Start

Tell me where the product is stuck.

In 30 minutes we look at where things stand, what you need from a CTO right now, and which option fits. Either way, you leave with a clear next step.

How the call goes

  1. 01You tell me about the product, the team and the next 6 months.
  2. 02I ask about the code, the stack and what keeps breaking.
  3. 03We pick the option that fits, or agree that none does.

09:00 to 20:00 CET

Founding rate: the first 3 clients get 20% off, in return for a named testimonial and a case study. On a monthly plan, the 20% applies to the first month.