Nullify

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Autofix

Security fixes
that won't break your codebase

Nullify writes a minimal, root-cause fix for every key finding, works the pull request through CI and review, and hands it to the right engineer to approve.

A fix only counts once it merges

324
patches merged in one month
for SmithRx
10,781
vulnerabilities fixed and merged
for our customers
−54%
less time to fix, from 11.8 days
to 5.4 days, across customers
100%
of fixes ready to merge
for a media customer
“It makes sense to automate this stuff with agents rather than hiring people.”
Michael Hensley, Head of Security

It fixes the problems that matter,
wherever they show up

What it fixes

Code, packages, cloud and API issues

Nullify fixes code at the line that causes the problem, updates vulnerable packages along with the code that uses them, fixes cloud settings in your infrastructure code, and closes API holes its pentest agent proved.

Fix candidates · triaged as real
code auth/session.ts · add ownership check
dependency jsonwebtoken → 9.0.2 · 3 call sites
cloud storage.tf · block public access
pentest POST /api/refunds · enforce tenant scope
Only issues confirmed as real get a fix
Leaked AWS key · config/deploy.yml
✓Routed to @j.chen. Rotation guidance attached.
manual fallback
ticket SEC-418 · filed ✓
owner · tagged ✓
no fix PR opened
Not autofixed

Leaked secrets get rotated, not patched

A leaked key has to be changed with the provider that issued it. Nullify sends it to the owner with steps to rotate it and a ticket to track it.

Every fix is checked before you see it

Nullify finds the root cause, makes the smallest change that fixes it, and writes it to match your code. A second review step then checks the fix before anyone on your team sees it.

01
Plan
02
Write
03
Review
04

Tested in your pipeline

Nullify runs the scans, builds and tests your pipeline already has, and shows the results on the pull request.

Draft PRParameterize the account filter
Reviewer @priya-k · wrote these lines
scanner · finding no longer reported
build · passing
tests · passing
independent review · minimal change
Results recorded on the PRChecked

Nullify stays on the pull request until it's ready to merge

If CI fails, it reads the logs and pushes a fix. If a reviewer leaves a comment, it replies. If the branch falls behind, it updates it. Developers can @mention Nullify to ask questions or request changes.

Nullify · remediation
→ PR #1311 · Parameterize the account filter
→ CI integration-tests failed … reading logs · corrective commit pushed
Slack · #payments-eng
Nullify2:14 PM

Fix PR #1311 is ready for review: an SQL injection in payments-api. CI is green and @priya-k is assigned.

Pull request · remediation
Ready for reviewacme/payments-api #1311
Parameterize the account filter
nullify opened this PR

Passes the account ID as a bound parameter instead of building the filter string, so untrusted input can't change the query. Matches the module's existing error handling.

root causeCI greenowner routed
›_ lib/query.ts+2 −1
14  function buildFilter(accountId) {
15  - return db.raw(`account_id = ${accountId}`)
15  + if (!isUuid(accountId)) throw new ValidationError()
16  + return db.raw("account_id = ?", [accountId])

Other tools suggest a patch, and Nullify gets it merged

Stays until merged

Most tools hand you a diff and stop there. Nullify stays on the pull request through CI and review until your team merges it.

Fixes only real issues
Fixes failing CI
Paced to your team
Fix PRs · payments-api3 open max
Pull requestCIReviewerState
Parameterize filter✓ green@priya-kready
Bump jsonwebtoken✓ fixed@opsready
Tenant scope✓ green@m.alvarezreview
Redirect checkqueued—waiting

Frequently Asked Questions

Does Nullify merge its own fixes?

No. Nullify gets a fix ready to merge, and someone on your team always decides whether to merge it.

What can Nullify fix?

Code vulnerabilities, vulnerable packages, cloud settings in your infrastructure code, and API issues Nullify has proven. Leaked secrets aren't fixed automatically, because they have to be rotated with the provider that issued them. Nullify sends those to the owner with a ticket instead.

How do I know a fix works?

Every fix goes through a separate review step. Then Nullify runs the scans, builds and tests your pipeline has and shows the results on the pull request. The pull request starts as a draft and is marked ready for review once CI passes.

What if CI fails?

Nullify reads the failure logs and pushes a fix. If the branch falls behind, it updates it.

Who reviews a Nullify fix?

Nullify picks up to three reviewers: first the people who wrote the code being changed, then the code owners, then the team that owns the repository.

Will Nullify flood us with pull requests?

No. It keeps at most three fix pull requests open per repository and opens at most five new ones per plan. The next fix opens when one is merged or closed.

Can developers ask for a different fix?

Yes. Reply on the pull request or @mention Nullify to ask why a change is needed or to ask for a different approach. It replies in the thread.

Scoped honestly

Your team always makes the merge call

Nullify never merges code on its own. It keeps at most three fix pull requests open per repository, so reviews stay manageable. When a fix can't be automated, it files a ticket with clear steps and tags the owner.