differential-review

Automated security code review scans pull requests and commits for vulnerabilities using git history and test coverage analysis. It identifies security regressions and generates comprehensive markdown reports with actionable findings for compliance tracking.

Yes, code analysis depth can be customized to adapt to the size of the codebase. This allows the security review to remain efficient and thorough whether scanning small commits or reviewing differential changes across a medium-sized project.

The best way to identify security regressions is by performing a differential review on code changes. By utilizing git history alongside test coverage analysis, you can detect newly introduced vulnerabilities and output detailed markdown reports for remediation.

Yes, automated code analysis works directly with git history and test coverage metrics to evaluate code changes. It scans commits and diffs to pinpoint security vulnerabilities, ensuring that new code regressions are caught before merging.

Running automated code analysis on diffs requires Read, Write, Grep, Glob, and Bash permissions. These permissions allow the review tool to access git history, scan files, and generate comprehensive markdown reports for security vulnerabilities.