Skip to main content
Every review belongs to one commit: the pull request’s head when the review started. If new commits arrive, that review describes code that has since changed; ask for another review with a command.

What Veridical posts

  • A pull-request review whose body is the review summary: the verdict in plain words, the safe-to-merge score of a complete review with what lowered it and which files it does not score, each finding with its severity and location, and how the review was done. It is posted as a comment review: it never approves and never requests changes. On the first review of a pull request it also lists the commands maintainers can use.
  • Inline comments on the changed lines for the findings Veridical approved as defects. Each names the affected code, what goes wrong, its severity, and the evidence behind it. Concerns that hold only under a condition are written out in the summary instead.
  • A check run named Veridical Review (advisory) on the reviewed commit, with the same summary. Its conclusion is always neutral, so on its own it never blocks a merge.
  • A second check run named safe-to-merge, only when the repository turns on the merge gate.

How a review is done

A review agent reads the pull request and the repository at the reviewed commit, in an isolated sandbox. For the ecosystems the sandbox supports, it can also build the code and run it, for example to call a changed function with an input that shows the problem. See Review limits for which ecosystems those are. Before anything is posted, a separate check classifies each finding. Findings that do not hold up are not posted. A finding that applies only under a condition says which condition. When a finding’s evidence records a run that reproduced the problem, the inline comment shows it on its own line:
That line reports the review agent’s own run. Veridical does not run it again itself, and it never adds the line when the evidence records no such run.

When a review does not complete

If Veridical cannot finish a review, the check says the review is incomplete and no findings are posted for it. An incomplete review gets no safe-to-merge score and is not counted against your allowance. A maintainer can try that commit once more with a command.

What a review is not

A review is advisory evidence. Veridical does not approve or merge the pull request, and a review with no findings is not a claim that the code has no defects. See Review limits.
If a result looks stale, incomplete, or duplicated, send the pull-request URL to contact@veridical.dev. Do not send tokens, private keys, or private source by email.
Last modified on November 17, 2026