Found Proven Fixed ✓ Proven fixed

Nullgap attacks your code and running apps in a sealed sandbox, reports only what it can exploit, and re-runs the same exploit against the fix. No proof, no finding.

Free 14-day trial · Sign in with GitHub · or talk to a security engineer

Maps how your data is handled to 31 standards and laws

SOC 2 Security GDPR Privacy ISO/IEC 27001 Security HIPAA Sector EU AI Act AI PCI DSS 4.0 Sector India DPDP Act Privacy NIST SP 800-53 / FedRAMP Security ISO/IEC 42001 AI UK GDPR Privacy CMMC 2.0 Security OWASP Top 10 for LLM apps AI CCPA / CPRA Privacy GLBA Sector HITRUST CSF Security NIST AI RMF AI LGPD Privacy FERPA Sector PIPEDA and Law 25 Privacy Colorado AI Act AI EU DORA Sector APPI Privacy PIPA Privacy Singapore PDPA Privacy Australia Privacy Act Privacy China PIPL Privacy COPPA Privacy Connecticut CTDPA Privacy Texas TDPSA Privacy Utah UCPA Privacy Virginia VCDPA Privacy

Where developers already work

GitHubSlackJiraVS CodeMCP for coding agentsREST APIWebhooksSSO and SCIMSARIF exportCSV export
Try it · 5 seconds

Can you spot the vulnerability?

Click the line you think is unsafe. Then see how Nullgap proves it, instead of just pointing at it.

Hint: who is allowed to see invoice 1002?

src/routes/invoices.ts

Stop triaging maybes.

Most tools hand you a list of things that might be wrong. Nullgap hands you the few that are, with the proof.

PossiblePossible SQL injection in report buildersrc/reports.ts:88
PossibleWeak hash function usedsrc/util/hash.ts:12
PossibleMissing authorization on routesrc/routes/invoices.ts:1
PossibleHard-coded secret in test fixturetest/fixtures/env.ts:3
PossibleOpen redirect in loginsrc/auth/login.ts:51
PossibleCross-site scripting in commentssrc/views/comment.tsx:20
Illustrative example.
Found

Nullgap reads your code and your running app the way an attacker would, and lists what looks exploitable.

Proven

Each lead is attacked in a sealed sandbox. Only what really works is reported, with the requests that prove it.

Fixed

Nullgap writes the fix, re-tests it on a fresh checkout and opens a pull request for your team to review.

✓ Proven fixed

The same exploit runs again against the fix. It has to fail before the finding is closed.

What “proven” means

A finding is a claim. A proof is four checks that all pass.

Nullgap marks a finding proven only when the attack works, works again, a harmless control doesn’t, and a separate review agrees. A status code alone never counts. Anyone on your team can replay it.

What happened · Order export returns any customer’s order (sample)
RunWhat it showedResult
Attack runCustomer A fetched customer B’s order exportWorked
Control runAn ordinary, harmless input behaved safelyNo effect
RepeatA second run gave the same resultWorked
Independent checkA separate reviewer agreed it shows the flawAccepted
After the fix: the same probe no longer reproduces it. Fixed, and proven fixed.
Products

One proof standard, from the pull request to the running app.

Pull request reviewEvery PR

Every pull request reviewed for security before it merges, with the proof attached when a flaw can be shown. Triage by replying in the PR.

Whitebox pentestProven

A full test of a repository from its code. Each finding is reproduced in a sealed sandbox you can replay. Price shown before it runs.

Live testing with real accountsProven

Point it at staging with up to five test accounts. The access matrix proves when one user can reach another user’s data.

AI app testingOWASP LLM

Thirty-two prompt-injection attacks against your chatbot or agent, caught when it leaks a secret or calls a tool it must not.

Supply-chain checksnpm · PyPI

Malicious and risky packages flagged during a pentest, with package rules you can enforce.

Verified fixes✓ Proven fixed

A fix pull request for each proven finding, re-tested against the original exploit before it is called fixed.

Expert reviewAdd-on

Ask a Nullgap security researcher to check a finding or a whole report by hand, with notes on the finding.

In Slack and your editorSlack · VS Code

Ask Nullgap about findings in Slack, and see proven findings and apply verified fixes in VS Code.

Get the price for your repository

Pentests are priced by the size of the code. We count it and email you the exact price and what would be tested. Nothing runs or is charged.

See a sample pentest report

The executive summary, full findings with proofs and fixes, and the attestation letter your auditors and customers ask for.

Proof shows up where your team works

The same four states in pull request comments, Slack threads, Jira issues and the editor.

GitHubSlackJiraVS CodeMCP for coding agentsREST APIWebhooksSSO and SCIM
Trust and compliance

Built for the security review your security team will run on us.

Every point below is something you can check in the product, the docs or your own audit log.

Why teams choose Nullgap
Only proven findings

Four checks must pass, so your team stops triaging false positives.

Replay every proof

The exact requests and sandbox output ship with each finding.

Fixes proven, not promised

The original exploit is re-run against each fix before it closes.

Code and running apps

Whitebox pentest, PR review and live testing under one standard.

Access control across accounts

Up to five identities per app, with a proven access matrix.

AI apps covered

Prompt-injection testing mapped to the OWASP Top 10 for LLM apps.

The price before it runs

Priced by code size, one free retest, refunds when a run fails on our side.

A researcher when you need one

Expert review by a Nullgap security researcher on request.

Fits the tools you have

GitHub, Slack, Jira, VS Code, MCP, API and webhooks.

How your code and data are handled
AI prompts and responses are never storedAI processing runs only with providers under zero data retention. If that can’t be confirmed, the run stops.
Credentials are never sent to the AI or storedSecrets found in your code are masked before storage and never sent for analysis.
Your source code is not keptA repository is checked out for a run and deleted when the run ends.
Exploits run in a sealed sandboxProofs run in an isolated environment with no outside network.
Live tests only reach what you approveEvery request is checked against your scope list, and private addresses are never reached.
Test accounts are sealedPasswords and tokens are encrypted for your workspace and never shown again.
Automatic deletionSet a retention period and stored data is removed when it ends.
Export and erase on requestAn owner can download everything stored for the workspace, and erase it, at any time.
Tamper-evident audit logEvery change is recorded with who made it and when, in a hash-chained log.
Access controlOwner, admin and member roles, SSO and SCIM, required MFA, and a fresh code for sensitive actions.
Support access is opt-in and auditedNobody at Nullgap reads your data unless an admin grants it for a set time, and every read is logged.
Incident notificationIf an incident affects your data, the contact you set is told without undue delay.
Mapped to 31 laws and standards

Pick the frameworks you answer to, and Nullgap shows how its handling of your data lines up with each one, control by control.

Security standards
SOC 2ISO/IEC 27001NIST SP 800-53 / FedRAMPCMMC 2.0HITRUST CSF
Sector rules
HIPAAPCI DSS 4.0GLBAFERPAEU DORA
Privacy laws
GDPRUK GDPRIndia DPDP ActCCPA / CPRALGPDPIPEDA and Law 25APPIPIPASingapore PDPAAustralia Privacy ActChina PIPLCOPPAConnecticut CTDPATexas TDPSAUtah UCPAVirginia VCDPA
AI governance
EU AI ActISO/IEC 42001NIST AI RMFColorado AI ActOWASP Top 10 for LLM apps

This is a mapping of how Nullgap handles your data, not legal advice or a certification. Using Nullgap does not by itself make your organisation compliant.

Evidence your auditors can use
  • Pentest attestation letter
  • Executive summary and full report
  • Evidence bundle for every finding
  • Audit log export
  • Findings export as CSV or SARIF
Nullgap’s own assurance
  • SOC 1 Type II In process
  • SOC 2 Type II In process
  • Data processing agreement with sub-processor list
  • Security questionnaire answers on request
  • Responsible disclosure policy
Request the security pack
Pricing

Priced in the open. You see the price before anything runs.

And the proof guarantee: if a pentest proves nothing, your next pentest of that repository is half price.

Estimate your price
Pentest
$2,500
Up to 250k lines · 150 fix credits
PR review
$975
a month, billed yearly
Live testing with up to 5 accounts and a free retest within 60 days are included in every pentest.Get the exact price
Free
$0
to see your first proof
  • 14-day trial of PR review
  • Watch a pentest find and prove
  • No card to start
Get a free proof
Pentest
From $750
per pentest, by size of the code
  • Proven findings and verified fixes
  • Live testing with up to 5 accounts
  • Free retest within 60 days
Get the price for your repo
Enterprise
From $36,000
a year
  • PR review, 4 pentests and AI app testing
  • Expert review of every report
  • SSO, SCIM, audit export, DPA, named engineer
Talk to a security engineer
Add-ons and usage
Expert review by a Nullgap researcher$250 / findingOr $2,500 for a whole pentest report. Included on Enterprise.
AI app testCreditsPrompt-injection run against one AI app; the most it can use is shown before it starts.
Fix runs beyond the included credits$1.50 / creditCharged only for work done; refunded if a run fails on our side.
Open-source projectsFreePR review on public open-source repositories.
Talk to a security engineer

See Nullgap prove a vulnerability in your stack.

A 30-minute call with an engineer, not a sales script. Bring a repository or a staging app and we’ll walk through a live proof.

  • Scoping for pentests and live testing
  • Security review and questionnaire answers
  • Enterprise terms: SSO, audit log, expert review

Questions security teams ask

Is my source code stored?

No. A repository is checked out for a run and deleted when the run ends. Findings keep the line they refer to and the explanation.

Is my code used to train AI models?

AI processing runs only with providers under zero data retention, so prompts and responses are not stored. If that can’t be confirmed, the run stops.

Will you attack production?

Proofs run in a sealed sandbox built from your code. Live testing only reaches addresses you put on your scope list, read-only unless you allow more.

What happens when Nullgap can’t prove something?

It isn’t reported as a finding. You can still see what was looked at and ruled out, so you know what was covered.

How is a pentest priced?

By the size of the code: $750 up to 50k lines, $2,500 up to 250k, $6,000 up to 1M, and a quote above that. You see the exact price before it runs, a retest within 60 days is free, a run that fails on our side is refunded, and if a pentest proves nothing your next one of that repository is half price.

Where is Nullgap on SOC 1 and SOC 2?

Our SOC 1 Type II and SOC 2 Type II audits are in process. Ask for the security pack for our current controls, data processing agreement and questionnaire answers.

Can we use it for our audits?

Yes. Pentests produce an attestation letter, an executive summary and a full report, and the compliance mapping shows how data is handled for the frameworks you choose.

✓ Proven fixed

Get your first proof today.

Connect a repository and watch Nullgap find, prove and fix. You only ever see what it could prove.

Get a free proof Book a demo