differential-review

Automate security code review by running a differential analysis on git history to detect vulnerabilities in pull requests. The review prioritizes authentication, cryptography, and value transfer flaws to prevent regressions before merging critical updates.

A differential security review evaluates code changes against git history to identify newly introduced vulnerabilities. You need it before merging critical updates, such as smart contract payment logic, to ensure no security regressions are deployed.

Yes, you can use this security audit on large codebases because the analysis depth automatically adapts to the codebase size. It leverages git history for context and calculates blast radius to assess risk across the project.

Calculate blast radius and check test coverage by analyzing the differential diff of code changes within the git history. This risk assessment identifies the potential impact of vulnerabilities and flags areas lacking sufficient test coverage.

Yes, this code review tool generates comprehensive markdown reports detailing identified security vulnerabilities. These reports document the differential review results, including risk assessment and test coverage gaps, to prevent security regressions.