sc-diff-report

To run an incremental security scan, you analyze only files changed in a git diff or recent commit to deliver focused feedback on touched code. This targets pull requests and branches to surface new vulnerabilities within the modified scope.

Finding security vulnerabilities introduced in a pull request requires diff-based vulnerability detection on touched files. This approach classifies findings as new or existing relative to the changed scope and highlights actionable remediation guidance.

Yes, you can analyze recent commits for security issues without scanning the whole repository by targeting only modified files from git diffs. This enforces phase-based analysis with change detection to produce a focused diff-ready report.

Incremental scanning does detect existing vulnerabilities within touched code and their context. It enforces phase-based analysis with change detection, classifying findings and surfacing both new and existing issues in the modified files.

A security diff report includes context, risk levels, and suggested mitigations for quick governance. It classifies vulnerabilities as new or existing relative to the touched scope and provides concise remediation guidance for changed code.

Diff-based vulnerability detection is not suitable for full codebase audits or baseline security assessments. It targets only modified files from git diffs, branches, and recent commits, meaning it ignores untouched code outside the current change scope.