Email contact@veridical.dev. We read every
message and answer within 24 hours.
Report a review or availability issue
If a review did not start or did not finish, look at the pull request on GitHub
first. When Veridical declines a review or cannot finish one, its check says why
and whether anything was counted. Also see
When Veridical reviews.
For a review problem, include:
- UTC time range;
- public repository and pull-request URL;
- installation or delivery identifier if visible;
- expected and actual review state;
- whether the pull-request head changed;
- a redacted screenshot or error message.
Do not include installation tokens, webhook secrets, App private keys, cloud
credentials, database URLs, or unredacted private artifacts.
Security and privacy
Use Security or Privacy in the subject for those requests. Do not include
exploit payloads, credentials, private keys, or sensitive personal data in the
first message; ask for a safe transfer channel. Last modified on November 17, 2026