Evidence for the code that landed.

Two matching bounded observations detect observed races, but the GitHub API is not an atomic snapshot. Exact candidate, check producer and attempt identities matter. Missing validation requirements do not become automatic VERIFIED. Unsupported queue requirements, including ALLGREEN other-entry evidence, cannot be waived.

HTML and JSON receipts expose the evidence and gaps. Eligible receipts can carry portable replay artifacts. Unsigned replay checks consistency over supplied inputs; it does not establish packet provenance or independently authenticate GitHub facts. Git-derived facts can be recomputed against a separately acquired repository copy.

Merge Proof does not guarantee correctness or security. The free local CLI and Action inspect local Git evidence; they do not collect the hosted service's CI execution, approvals or remote-ref evidence.

Don't trust Merge Proof more than necessary. See the exact authority before connecting.

Standard GitHub App repository access

• Read: Actions, Administration, Commit statuses, Contents, Merge queues, Pull requests, and GitHub's mandatory Metadata permission. These reads collect workflow/check evidence, repository rules, Git identities, merge-queue state, PR state, and landed content identifiers.
• Checks: read and write. Read check results and publish or update this App's Merge Proof Check output; it cannot change repository files.
• Organization members: read. Verify that the signed-in billing user is an organization owner.

GitHub sign-in: the OAuth request adds no extra OAuth scopes. Its short-lived user token is kept in process memory while Merge Proof checks identity, App installations, authorized repositories, and organization-owner status.

Technical access and processing: Contents read is real source access. GitHub responses can include workflow text and diff patches, and reconstruction fetches exact Git objects into a private partial bare mirror. Merge Proof uses these inputs to bind identifiers, inspect workflow action references and deterministically reconstruct trees; it does not execute customer code.

Persistence and AI boundary: receipts retain normalized evidence, identifiers, paths, hashes, rules, checks, reviews, actors, workflow provenance and reconstructed Git facts. Exact Git objects and receipt references are retained for replay. Git may materialize reachable blobs. Active receipt eviction does not delete the historical archive. Incidental API patch text and decoded workflow text are not written into receipts. No source contents are sent to an LLM or AI provider; no AI model decides the verdict.

Write authority: the standard grant does not include Contents write, Secrets, Workflows write or organization administration. It cannot push commits, change branches or files, merge or close PRs, post PR comments, alter repository settings, edit branch protection/rulesets or modify Actions workflows. A separate optional Enhanced Policy Proof companion, if explicitly enabled later, has repository Administration write authority but is constrained by Merge Proof to policy reads; it is not part of this standard connection.

After uninstall or revocation: new collection stops and hosted access fails closed because current installation/repository access is rechecked. Historical receipts, evidence, retained Git objects, account records and operational backups are not automatically erased; current code has no customer-selectable deletion deadline or automatic uninstall purge. Private access follows current repository authority, not only billing ownership. Uninstall does not make retained evidence public.

The first CURRENT, collection-complete VERIFIED or NOT_PROVEN hosted receipt starts seven calendar days, exactly once. NOT_PROVEN means evidence is missing; it does not mean your code is broken. Failed, unavailable or stale collection does not start the clock. Connecting GitHub, installing the App, authorizing repositories and historical scans do not start it either.

One trial is shared across installations owned by the same GitHub account. Reinstalling or refreshing the same head does not restart it.

The trial does not enable new enforcing policies. New enforcement requires paid Pro and a repository administrator; GitHub must separately require the correct Merge Proof Check. Merge Proof never edits branch protection or rulesets.

Previously configured enforcing policies remain enforced. At hosted expiry they report failure; report-only notices are neutral. If GitHub requires the check, subscribe or remove that required check. Provider or permission failures can prevent delivery; automatic unblocking is not guaranteed. A passing policy Check is not necessarily a VERIFIED receipt.

Distinct human GitHub IDs observed opening covered PRs or pushing covered commits. Bots, configured service identities and inactive organization members are excluded. One human counts once across the paying account’s installations. Initial pricing uses the preceding 30 days of observed covered activity; subsequent counts use the subscription month. Review the count before checkout. Increases require confirmation; changes take effect at renewal without proration.

Look back at what available evidence can establish about previous merges. The free scan covers up to 5 merged PRs among the 30 most recently updated closed PRs. Unsupported history stays unavailable. Current rules cannot establish historical approval validity. One bounded scan does not start the trial or count bugs prevented. Squash/rebase reconstruction and historical approval validity may be unsupported or unavailable. New scan collection pauses when hosted access expires.