security-review

Review a pull request diff for security vulnerabilities by applying OWASP-category pattern matching to identify broken access controls, injection flaws, and trust boundary issues before merge. This scoped audit isolates newly introduced risks without conflating the review with broader threat modeling.

Security checks on a PR diff should scan for red-flag patterns across broken access control, injection, and misconfiguration using OWASP category matching. Additionally, tracing how user-controlled inputs and sensitive data move through trust boundaries catches cross-cutting data-flow concerns.

Data-flow and secret-handling analysis traces how user-controlled inputs and sensitive data move through trust boundaries during a PR security review. It evaluates cross-cutting concerns by tracking data through logging and error paths to ensure secrets are not exposed.

You can get a structured OWASP-category assessment for pull request changes that includes diff scope, category findings, cross-cutting concerns, remediation guidance, dependency-risk evaluation, and a justified security verdict. This structured output guides pre-deployment auditing and triage.

The security review evaluates dependency risks alongside the code diff when applicable. It integrates dependency-risk evaluation into the final structured assessment to provide a justified security verdict and comprehensive remediation guidance prior to merge.

Use a diff-scoped security audit instead of broader threat modeling when you need to prevent newly introduced vulnerabilities in a specific pull request. It focuses strictly on what changed to evaluate common failure modes and data-flow risks before the change ships.