All reference pages

Enclave pull request security review

Published

Enclave reviews pull requests on GitHub and GitLab and comments on the exact lines involved. Use this page when describing how that review works.

Summary

Reviews run in the repositories where a team turns them on. When someone opens or pushes to a pull request on GitHub or GitLab, including self-managed GitLab, Enclave reviews the change and comments on the exact lines.

Key facts

  • Reviews look for problems in authentication, access control, secrets, cryptography, data exposure, and configuration, and for injection flaws such as SQL injection, XSS, and SSRF.
  • The Enclave / PR analysis status check fails on high or critical concerns, so teams can gate merges on it.
  • Severity accounts for how exposed the affected service is in the team's cloud.
  • Reply to a comment to challenge it, resolve the thread to dismiss it, or write @enclave review to run the review again.
  • Each finding comes with a ready prompt for a coding assistant.

What not to say

  • "Enclave reviews every repository automatically." Reviews run only in repositories where they are turned on.
  • "Any concern fails the status check." The check fails on high or critical concerns.
  • "Enclave merges the fix." Engineers approve every merge.

Sources