Skip to main content

Repository permissions

The Veridical.dev GitHub App requests five repository permissions, one organization permission, and one account permission. The last two are for signing in to Veridical; see Sign-in permissions. Veridical does not request repository administration, Actions secrets, workflow write, deployments, or environments. It does not approve or merge pull requests.

Sign-in permissions

You sign in to Veridical with your GitHub account. GitHub shows its own consent page the first time, and you come back to app.veridical.dev. GitHub asks you to approve Email addresses when you authorize Veridical. An organization owner approves Members for the organization’s installation. If they have not, the installation keeps working, and people join a Team workspace by invitation or wait until an admin adds them. Veridical reads organization membership only for people who sign in to Veridical, at sign-in and about once a day while they stay signed in. It never receives your GitHub password and does not keep the GitHub token issued at sign-in.

Why Veridical asks for contents write

Reviews only read your code. The worker that runs a review receives a short-lived token for that one repository with read-only contents access, and a review never pushes commits, creates branches, or changes files. Free reviews never use write access. Write access exists for one feature: verified fixes, on plans that include repair. When a workspace member asks Veridical to fix a completed review, Veridical creates a new branch from the reviewed head commit and opens a separate pull request with the verified change. It never pushes to the contributor’s branch and never merges. GitHub grants an app’s permissions for the whole installation, so the install screen shows write access to code even if you never request a fix.

Check runs

Each review posts one check run, Veridical Review (advisory), with a neutral conclusion, so it never blocks a merge. A repository that turns on the merge gate also gets a safe-to-merge check run on the same commit, which passes or fails and which your branch protection can require.

Webhook events

GitHub also sends installation and repository-selection events to every app installation, and tells the app when someone revokes its authorization, which ends their Veridical sign-in sessions. See When Veridical reviews for the exact triggers.

Publication safety

  • Work is bound to an immutable base and head.
  • A moved head makes the earlier result stale and prevents it from becoming the current review.
  • Comments are published only for findings that survive verification.
  • Duplicate webhook deliveries are idempotent.
  • Commands are accepted only from people GitHub reports as having write, maintain, or admin access to the repository.
Uninstalling the app or removing a repository stops new work for that scope. For what Veridical receives, keeps, and publishes, see Data handling.
Last modified on November 19, 2026