security-review

Run a security review by applying differential analysis to your pull request to identify regressions, calculate blast radius, and generate an evidence-backed markdown report with severity, attack scenarios, and remediation recommendations.

Blast radius calculation in differential code analysis counts callers of modified code and classifies impact severity to prioritize high-risk changes, helping reviewers decide whether to block or require remediations before merge.

Git blame traces are used to track removed code during differential security reviews, providing evidence-backed findings that show exactly what was deleted and its potential impact on authentication, crypto, or payment logic.

Generate a markdown security report for pre-deployment diffs by analyzing code changes, checking test coverage status, building adversarial attack scenarios for high-risk changes, and outputting concrete remediation recommendations.

Differential security review works with pull requests, commit ranges, and pre-deployment diffs, applying risk-first analysis to changes affecting external calls, validation, and user-data handling to surface regressions.

Automated adversarial modeling focuses on high-risk changes by building concrete exploit scenarios, but reviewers must still interpret the generated attack scenarios and per-file risk scores to decide whether to approve or block a merge.