differential-review

Perform a security-focused differential code review by analyzing PRs, commits, and diffs to identify potential vulnerabilities and regressions, generating a structured markdown audit report.

Blast radius calculation quantitatively assesses the security impact of code changes by analyzing call graphs and dependency usage to determine the extent of potential vulnerabilities.

Generate exploit scenarios for high-risk code changes through adversarial modeling, which builds concrete attack simulations prioritizing modifications to authentication, cryptography, and external calls.

Yes, you can review pull requests modifying authentication modules to ensure no security invariants are broken, verify test coverage sufficiency, and validate rigorous security protocols.

Prioritize code changes for security audits using a risk-first analysis methodology that targets modifications involving authentication, cryptography, and external calls to scrutinize critical paths.

Yes, differential security reviews require git history integration to satisfy requirements for evidence-based findings, ensuring vulnerabilities are tracked through commits and structured audit reports.