Start here
What Nullgap does
What Nullgap is, the four things it does, how you reach it, and where to start.
Nullgap is a hosted security review service for your source code. It reads the code you connect, reports flaws an attacker could use, and shows how far each one was checked: reproduced, independently reviewed, or neither.
Every finding carries one of three assurance levels, proven, verified or unverified. They are defined on Core ideas and mean the same thing everywhere in the product and in these pages.
#The four things it does
#Pull request security review
When a pull request opens or gets new commits, Nullgap reviews the change together with the code around it. The result appears on the pull request as a check, a summary comment and inline comments on the changed lines. A review with nothing to report posts no comment.
Start with the pull request review quickstart, then read what is reviewed.
#Whitebox pentests with proof
A pentest is a full assessment of one application from its source code at a version you choose. Candidate findings are independently reviewed, and the most serious ones are reproduced with a probe in an isolated sandbox. You get the findings, a full report, an executive summary and an attestation letter, and one retest is included.
Start with the first pentest quickstart, then read proof and coverage.
#Live testing inside an agreed scope
A pentest can also try its findings against a running deployment, such as a staging environment. Nullgap only sends requests to hosts on your organisation's scope list, and it only reads unless you confirm that the target is disposable. See live testing.
#Verified fixes
For an open finding, Nullgap can write a fix, check it, and hand it to you as a pull request or as a suggested change on the pull request under review. Nothing is merged for you. See verified fixes.
#How you reach it
| Way in | Use it for | Where to read more |
|---|---|---|
| Console | Connecting code, reading findings, triage, starting pentests, settings | Getting started in a new workspace and the quickstarts in this section |
| REST API | Reading findings, reviews and pentests, triage, starting pentests and fixes, and settings, from your own tools | API overview and the API reference |
| Outbound webhooks | Being told when a review or pentest finishes or a finding changes | Webhooks |
| MCP server | Letting a coding agent read findings and start fixes: add the address, sign in, approve | MCP server |
| CLI | Working from a terminal or a build pipeline | CLI and CI |
The API samples on this site use three environment variables: NULLGAP_URL (the address of your Nullgap console, with no trailing slash), NULLGAP_ORG (your organisation's slug) and NULLGAP_API_KEY. Creating a key is described on API keys.
#What it is not
- Not a guarantee that code is free of flaws. A review or pentest reports what it found and says what it covered. A run that could not finish its work says so instead of reporting a pass.
- Not a replacement for your own review of a fix. A fix is checked before you see it, and then it waits for a person to merge it.
- Not a production scanner. Live testing is meant for staging deployments you own or are authorised to test, with test accounts.
- Not a dependency inventory. Published advisories against the packages you pin are listed apart from findings, because nothing showed that your application can be attacked through them. See advisories and findings.
- Not able to review pull requests on code it can only read. A public repository added by address or an uploaded archive can be pentested, and nothing else. See connecting your code.
#Where to go next
- Read Core ideas. It is the vocabulary for the rest of the site and takes a few minutes.
- Connect a code host: which way to connect.
- Follow one quickstart: a first reviewed pull request or a first pentest.
- Learn to read a finding and to triage.
- Look at skills: the packaged capabilities reviews and pentests use, which you can also run on demand and extend with your own.
A new workspace opens with a guide that walks through the first three; see getting started in a new workspace. When you are stuck, the support channel is in the console under Help.
If you need to know how your code is handled before you connect anything, read code handling, the sandbox and AI processing.
Nullgap documentation