security-review

To run a security review on a GitHub pull request, trigger the review command with the PR number to analyze authentication, secrets, and input-handling risks. The review applies a severity-based checklist to generate a pass, conditional, or fail verdict.

A PR code security check identifies secrets exposure, injection risks, XSS patterns, authorization gaps, and insecure cryptography. It specifically targets pull requests handling user data, API endpoints, and third-party integrations to prevent vulnerable code from merging.

Yes, you can persist audit trails for security reviews across multiple pull requests. The review process saves structured audit artifacts and renders a review trend section to make security changes legible across PR history.

Automated vulnerability scanning escalates high-risk security issues by invoking a Security Auditor for sensitive areas like auth, crypto, and PII. It further escalates critical threats to a Head of Security or Penetration Tester role.

The best way to detect exposed secrets in a pull request is using an automated security checklist that scans code changes for credentials. It flags insecure practices and posts a GitHub review with a severity-backed fail or pass verdict.

You need a security-focused code review on API endpoints when a pull request introduces changes to authentication, data storage, or third-party integrations. This prevents injection risks and API security gaps from reaching production.