FindSpot risk in code and cloud
ProveConfirm what's exploitable
FixShip fixes that get merged
Nullify never merges. A developer approves every fix.
Learn
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.
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.
“It makes sense to automate this stuff with agents rather than hiring people.”
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.
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.
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.
Nullify runs the scans, builds and tests your pipeline already has, and shows the results on the pull request.
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.
Fix PR #1311 is ready for review: an SQL injection in payments-api. CI is green and @priya-k is assigned.
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.
Most tools hand you a diff and stop there. Nullify stays on the pull request through CI and review until your team merges it.
No. Nullify gets a fix ready to merge, and someone on your team always decides whether to merge it.
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.
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.
Nullify reads the failure logs and pushes a fix. If the branch falls behind, it updates it.
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.
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.
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.
Related: Remediation docs · Triage & Remediation · Security Program Management · Exploit Validation
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.