Compliance platform

Hyperproof's Hypersync for GitHub records who reviewed the pull request. Aevral reads what it changes.

Hyperproof's Hypersync for GitHub collects pull requests with the reviewer, the review state and the approval settings. Aevral adds a security reading of the diff.

There is no native integration between Aevral and this platform today, and Aevral has no findings file to hand over. What exists is the pull request itself. Aevral is not affiliated with or endorsed by this platform.

This page covers one documented GitHub test or data feed of Hyperproof. Hyperproof offers other products and integrations not described here.

What Hyperproof reads or records

Hyperproof's Hypersync for GitHub collects a Pull Requests proof type whose fields include who reviewed it, the state of the review, its message and when it was submitted, plus a Branch Protection proof with the required number of approvals. It is a record of who reviewed, the state of that review, and the approval rule.

What Aevral reads

Aevral reads the change they reviewed and looks for security flaws: a diff that widens who can access what, or carries injection, XSS, SSRF, path traversal or an LLM-integration flaw. Its comments sit on the same pull request, in your GitHub history, where the reviewer can read them.

Hyperproof looks at, per its docs

  • Pull requests with title, URL, merge time and who merged.
  • Who reviewed, the review state, the message and when it was submitted.
  • Branch protection and ruleset settings, including required approvals.

Aevral on the same pull request

  • Aevral is an AI security reviewer for GitHub pull requests, live on install: installing the App starts reviews, and the owner can turn them off.
  • On each supported pull request it posts a GitHub Check named Aevral review. The Check is advisory: it always concludes neutral and never blocks a merge.
  • At most two findings per review, as inline comments on the added lines. A finding is a lead with evidence (the file, the lines, the reason to look), not a verdict. A human decides.
  • Those comments stay on the pull request, in your own GitHub history, next to the approval.

Run them together

Keep Hyperproof collecting the review record; let Aevral add a security reading of the same pull requests.

Aevral PR security review; everything Aevral works alongside.

Sources

Quoted from Hyperproof's public documentation. Hyperproof may change its product; check the page for the current wording.

  1. Reviewed By: Reviewer, State, Message, Submitted At help.hyperproof.app, retrieved 2026-09-29.
  2. Require a pull request before merging, Required number of approvals help.hyperproof.app, retrieved 2026-09-29.
  3. Pull Request, Title, URL, Merged At, Merged By help.hyperproof.app, retrieved 2026-09-29.
  4. Hypersync for GitHub help.hyperproof.app, retrieved 2026-09-29.

Other compliance platforms


Security review, handled.

Install the GitHub App and PR review starts on. Sign in with GitHub to connect it, then press Scan for the repository you already have.

Install the GitHub AppLog in

For professional use. By installing, you confirm you can act for the account or organization that owns it, and you accept the Terms and DPA on its behalf.