The bug isn't in the diff

Checking PR for known risky code is a solved problem; a lot of security scanners flag things like eval and passwords written into the code. But what about changes that happen beyond your diff?

That's where Zairo comes in!

It can see the ripple effects of the code changes or your diffs.
For example:

You changed something in function A; diff shows that, but what about function B, which is dependent on function A, and it got introduced a vulnerability?
That’s what Zairo takes care of

It follows a git diff through the call graph and has an LLM review the code the change affects. It can take your uncommitted code and find every class and function. For each one, it shows a model:

1. the code after the change and the lines the change removed.

2. the functions that call it and the functions it calls.

3. how it can be reached from where outside input comes in, such as web routes, command-line commands, and background jobs.

Then it asks the model what the change newly lets an attacker do. Zairo works with any model that LiteLLM supports, in the cloud or on your own machine, and pretty much any language.