Skip to main content
  • A completed review can still miss defects.
  • A stale, failed, cancelled, or incomplete result is not a clean result. An incomplete review has no safe-to-merge score, and with the merge gate on its safe-to-merge check fails.
  • Safe-to-merge is advisory. Veridical never approves or merges a pull request; the merge gate blocks a merge only when your branch protection requires it.
  • Repository content is untrusted. The review runs in an isolated sandbox with restricted network access. For private repositories, web access is limited by default to an allowlist of documentation sites.
  • The sandbox can build and run Python, JavaScript and TypeScript (npm, pnpm, Yarn), Ruby (Bundler), Go, and C or C++ (make, CMake). It has no Java, Kotlin, Rust, or .NET toolchain, so reviews of code in those languages read the code without building or running it.
  • A run can still be skipped when a dependency cannot be installed or a safe way to run the code is not available. The review then rests on reading the code, and its findings say so.
  • A pull request over 20,000 changed lines, or with more than 500 changed files, is not reviewed automatically. See How reviews are counted.
  • A review takes minutes, not seconds, and a large pull request takes longer.
  • GitHub (github.com) is the only supported code host.
If Veridical cannot finish verifying a review, it posts no findings for it and says the review is incomplete. That review is not counted, and a maintainer can try once more with a command.
Last modified on November 17, 2026