differential-review

To perform a security-focused differential review on a pull request, analyze the code changes to identify security regressions and vulnerabilities by evaluating blast radius and test coverage. The review adapts analysis depth to codebase size and generates a comprehensive markdown report.

Blast radius evaluation in code security analysis calculates the potential impact scope of code changes across a codebase. It is used during differential review to quantify the reach of modified code and generate evidence-backed markdown reports for stakeholders.

Yes, you can use git history to provide context for security code reviews. The differential review process utilizes git history alongside test coverage assessment to analyze commits and PRs, scaling analysis depth from triage to deep context to identify security regressions.

Yes, differential review works for large codebases by automatically adapting its analysis depth to codebase size. It scales from triage to deep context analysis across PRs, commits, and diffs of varying sizes to detect and prevent security regressions.

To generate an audit report for security vulnerabilities found in a diff, perform a differential review that calculates blast radius and checks test coverage. This process automatically produces a comprehensive markdown-based audit report suitable for stakeholders.

Checking test coverage when analyzing security regressions in commits ensures that modified code paths are adequately validated before deployment. Test coverage assessment is integrated into the differential review to evaluate the safety and blast radius of git commits.