Reviewer Externalby Peerivo
English

Independent security gate for GitHub, GitLab + GitVerse

Security review that sees beyond the diff.

Reviewer External inspects the pull request, repository structure, CI/CD, dependencies and SaaS runtime boundary. It never executes reviewed PR code and never treats incomplete coverage as success.

No PR code executionFail-closedExact HEADSaaS runtime

GITHUB · GITLAB · GITVERSE

Connect Reviewer in three steps

Choose a platform, authorize access to the repositories you select, and verify the connection. No personal access tokens, pasted YAML or manual webhook setup.

  1. 1Authorize with your code-hosting platform.
  2. 2Select repositories and save the connection.
  3. 3Create or update a PR/MR and read the report there.

GitHub

Install the GitHub App and choose repositories. PRs receive a Check Run and comment; direct pushes to the default branch are also reviewed.

Connect GitHub

GitLab

Sign in with GitLab and select projects you manage. Merge request results appear in GitLab.

Connect GitLab

GitVerse

Authorize GitVerse, select repositories and optionally enable the HIGH/CRITICAL merge gate. Webhooks and optional CI are provisioned by the installer.

Connect GitVerse

Connected does not mean reviewed. Create or update a PR/MR; to prevent merges, verify the CI run and configure branch protection.

Open connection center

Where will I see the report?

GitHub: PR Check Run and comment. GitLab: merge request result. GitVerse: PR comment and a separate CI status when Hard Merge Gate is enabled. A failed CI run or missing access is not PASS.

01 / REVIEW

What it checks

Not just syntax and style. Reviewer targets changes that become dangerous in real infrastructure.

Secrets & credentials

High-confidence token, private-key and production credential patterns in added lines.

CI & permissions

Unsafe pull_request_target usage, write-all, new OIDC permissions and workflow privilege expansion.

Migrations

Migration files without a controlled GitHub Actions execution path can fail the gate.

Dependencies

Lockfile drift plus new package, repository, image, domain and dependency relations.

Runtime boundary

RLS, customer secrets, webhooks, admin/control-plane and infrastructure configuration are reviewed as a separate security surface.

Coverage

Truncated trees, unavailable repositories or partial scans become findings instead of a green check.

SaaS / RLS

Checks tenant isolation, PostgreSQL RLS/FORCE RLS, admin/control-plane boundaries and provider-backed runtime evidence.

Webhooks & containers

Detects replay/idempotency gaps, unsafe customer-token storage, privileged/host networking, Docker socket mounts and unpinned container images.

02 / RELATIONS

Sees the security boundary beyond the diff

Reviewer connects PR changes to workflows, packages, images, OIDC and runtime surfaces inside the reviewed repository. This exposes privilege expansion, unsafe supply-chain changes and infrastructure risk before merge.

GETdedupeTTLepochRetry-After

03 / API SAFETY

Fast without false confidence

Successful GitHub GETs are cached only inside the trusted run, identical in-flight requests are deduplicated, exact-SHA content uses a separate TTL, and mutations advance the cache epoch. Rate limits and Retry-After are respected; if authoritative coverage cannot complete, the result fails closed.

04 / FLOW

How it works

1. Connect

A GitHub App receives only the repository permissions required for review.

2. PR event

A signed webhook dispatches a trusted reviewer worker.

3. Analyze

The worker reads authoritative base/head, diff, workflows and bounded security-relevant files through the GitHub API without executing PR code.

4. Gate

A GitHub Check Run and idempotent report expose findings and can block merge.

05 / RUNTIME

SaaS runtime security

Reviewer 0.3 checks tenant isolation, PostgreSQL RLS/FORCE RLS, customer secrets, webhook replay/idempotency, admin/control-plane, host/container/Kubernetes and supply-chain controls. Runtime-only assurances require provider-backed evidence.

06 / PRICING

Pricing

14-day free trial after verified card linking. Then pay the plan and actual overages at month end.

14 days free · card required

01

Starter

For a small team that needs an always-on PR security gate.

999₽/mo

Card linking required · no plan charge for the 14-day trial

  • Up to 5 active repositories
  • Up to 500 PR reviews/month
  • Secrets, CI, migrations, dependencies
  • 30-day review history
Start →

03

Business

For multiple teams with higher security coverage needs.

7 999₽/mo

Card linking required · no plan charge for the 14-day trial

  • Up to 75 active repositories
  • Up to 10,000 PR reviews/month
  • Host/container/supply-chain checks
  • Custom policy packs
  • Priority support
  • 365-day review history
Choose Business →

04

Enterprise

For large organizations and isolated environments.

On request

Annual Enterprise / on-premise license · request a quote

  • Custom repository and PR limits
  • Isolated / self-hosted deployment
  • Custom policy packs and runtime evidence
  • SLA and dedicated onboarding
  • Custom rules and integrations
Contact sales →

How billing works

  • A verified saved card is required before the 14-day trial; payment details stay with the payment provider.
  • At calendar month end, the plan is charged for paid days together with actual usage overages.
  • Overages: RUB 199 per extra active repository/month and RUB 499 per additional block of up to 1,000 reviews.
  • Available credit and eligible promo codes reduce the invoice; recurring charges require separate consent.
  • Enterprise / on-premise is available only by individually quoted annual license.

07 / FAQ

FAQ

Does Reviewer execute pull request code?

No. Reviewed code is treated as untrusted input and is read through the GitHub API.

What happens when a scan is incomplete?

Reviewer does not hide gaps. A critical coverage gap becomes a finding and can stop merge.

Do customers need Peerivo Global Contract?

No. Reviewer External is standalone for customers; Peerivo's internal Global Contract only governs Peerivo development.

Can it run in a Russian infrastructure contour?

Yes. Deployment can be isolated in the selected infrastructure; the website includes a static Nginx target for REG.RU.

What gets installed in GitHub?

Only a GitHub App. Customers do not add an Action or receive the proprietary analyzer: the App reads bounded data through the GitHub API and the private Reviewer service performs the analysis.