differential-review

Automate security code review for pull requests by analyzing diffs, prioritizing high-risk areas like authentication and cryptography, and generating markdown reports with vulnerability findings, attack scenarios, and remediation recommendations.

A security-focused differential review analyzes code changes in commits and pull requests using git history to detect vulnerabilities, calculate blast radius, and prevent security regressions before new code is merged into the main branch.

Yes, this differential review process leverages git history to provide context, analyzes codebase size to adapt depth, calculates the blast radius of potential vulnerabilities, and checks test coverage to assess the impact of code changes.

The best way to perform a security audit on a code diff is to adapt the analysis depth to the codebase size, check test coverage, prioritize high-risk areas like value transfer, and output a comprehensive markdown report detailing findings and recommendations.

Code review depth must adapt for large codebases to maintain efficiency, leveraging git history for contextual analysis while calculating the blast radius of changes to focus security checks on the most critical vulnerabilities and regressions.