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 GitHubIndependent security gate for GitHub, GitLab + GitVerse
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.
GITHUB · GITLAB · GITVERSE
Choose a platform, authorize access to the repositories you select, and verify the connection. No personal access tokens, pasted YAML or manual webhook setup.
Install the GitHub App and choose repositories. PRs receive a Check Run and comment; direct pushes to the default branch are also reviewed.
Connect GitHubSign in with GitLab and select projects you manage. Merge request results appear in GitLab.
Connect GitLabAuthorize GitVerse, select repositories and optionally enable the HIGH/CRITICAL merge gate. Webhooks and optional CI are provisioned by the installer.
Connect GitVerseConnected does not mean reviewed. Create or update a PR/MR; to prevent merges, verify the CI run and configure branch protection.
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
Not just syntax and style. Reviewer targets changes that become dangerous in real infrastructure.
High-confidence token, private-key and production credential patterns in added lines.
Unsafe pull_request_target usage, write-all, new OIDC permissions and workflow privilege expansion.
Migration files without a controlled GitHub Actions execution path can fail the gate.
Lockfile drift plus new package, repository, image, domain and dependency relations.
RLS, customer secrets, webhooks, admin/control-plane and infrastructure configuration are reviewed as a separate security surface.
Truncated trees, unavailable repositories or partial scans become findings instead of a green check.
Checks tenant isolation, PostgreSQL RLS/FORCE RLS, admin/control-plane boundaries and provider-backed runtime evidence.
Detects replay/idempotency gaps, unsafe customer-token storage, privileged/host networking, Docker socket mounts and unpinned container images.
02 / RELATIONS
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.
03 / API SAFETY
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
A GitHub App receives only the repository permissions required for review.
A signed webhook dispatches a trusted reviewer worker.
The worker reads authoritative base/head, diff, workflows and bounded security-relevant files through the GitHub API without executing PR code.
A GitHub Check Run and idempotent report expose findings and can block merge.
05 / RUNTIME
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
14-day free trial after verified card linking. Then pay the plan and actual overages at month end.
14 days free · card required01
For a small team that needs an always-on PR security gate.
Card linking required · no plan charge for the 14-day trial
02
For a product team with multiple repositories.
Card linking required · no plan charge for the 14-day trial
03
For multiple teams with higher security coverage needs.
Card linking required · no plan charge for the 14-day trial
04
For large organizations and isolated environments.
Annual Enterprise / on-premise license · request a quote
07 / FAQ
No. Reviewed code is treated as untrusted input and is read through the GitHub API.
Reviewer does not hide gaps. A critical coverage gap becomes a finding and can stop merge.
No. Reviewer External is standalone for customers; Peerivo's internal Global Contract only governs Peerivo development.
Yes. Deployment can be isolated in the selected infrastructure; the website includes a static Nginx target for REG.RU.
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.