Compliance platform

Sprinto's GitHub peer review check looks for enforced peer review. Aevral reads what the pull request changes.

Sprinto's GitHub App checks that peer review is enforced on every merge request to the main branch. 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 Sprinto. Sprinto offers other products and integrations not described here.

What Sprinto reads or records

Sprinto's GitHub App runs a check named Peer review should be enforced for code changes, and its fix reads: peer review should be enforced on every change merging request on the main branch. The check is about the rule on the branch: a peer has to look.

What Aevral reads

Aevral gives the peer something specific to look at when it finds one: a query built by string concatenation from request input, a server-side fetch of a user-supplied URL, or a session token that no longer expires. At most two findings per review, each a lead with evidence, and the peer Sprinto requires decides.

Sprinto looks at, per its docs

  • Whether peer review is enforced on merge requests to the main branch.
  • Branch protection and whether merges require passing status checks.
  • Commits and pull requests in the connected organization.

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 Sprinto's peer review check on the main branch; let Aevral add a security reading of the same pull requests.

Aevral PR security review; everything Aevral works alongside.

Sources

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

  1. Peer review should be enforced on every change merging request on the main branch. docs.sprinto.com, retrieved 2026-09-29.
  2. Branch protection and peer review enforcement docs.sprinto.com, retrieved 2026-09-29.
  3. Peer review should be enforced for code changes docs.sprinto.com, retrieved 2026-09-29.
  4. Merging of code changes should require passing status-checks docs.sprinto.com, retrieved 2026-09-29.
  5. Sprinto retrieves the following data: Installation ID Organisation details Repositories and branches Commits and pull requests docs.sprinto.com, 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.