differential-review

You can detect security vulnerabilities in a pull request by running a differential review that analyzes the git diff, evaluates blast radius, and generates an evidence-backed markdown report. This structured process identifies regressions and unsafe modifications in software updates.

Blast radius evaluation in security code analysis measures the potential impact of code changes by applying adversarial thinking and analyzing git history. It helps reviewers assess the risk and safety of modifications to authentication, cryptography, and external calls.

Yes, you can use differential review for commits and diffs without a full pull request. The security-focused diff analysis applies to various code changes, evaluating test coverage and identifying security regressions in software modifications.

The best way to generate a security review report for code changes is to perform a structured differential review that produces evidence-backed markdown reports. These reports include findings, attack scenarios, and confidence limits for engineering teams.

Yes, differential review assesses test coverage for security-sensitive modifications. It evaluates test coverage alongside git history and blast radius calculations to ensure the safety of changes to authentication and cryptography.