Skip to main content
Safe-to-merge combines calibrated finding risk, analyzer and execution coverage, and evidence quality. The result contains a decision, probability/score inputs, coverage measures, thresholds, reasons, and abstention state. It is deliberately advisory:
  • It never merges a pull request by itself.
  • It does not assert that unexecuted behavior is correct.
  • It abstains when coverage is below policy, inputs are incomplete, or required execution cannot run.
  • Repository config can tighten thresholds but cannot make them more permissive than defaults.
Treat a positive result as evidence that the reviewed change satisfied the configured decision rule—not as a proof that the software has no defects.
Last modified on July 28, 2026