Reviewpad must be presented as history, not a current standalone AI code-review recommendation. Its own GitHub organization states the project was shut down after Snyk acquired it in October 2023; remaining docs and app listings are archival traces of previous functionality.
What the product actually does
Reviewpad described a policy-driven pull-request process: assigning reviewers, labeling work, checking descriptions and enforcing team conventions. The archived documentation describes a 5-minute onboarding flow and Reviewpad Check. The GitHub App listing now marks the app maintenance-only and says new installations are unavailable. These statements explain why a static directory entry can mislead a buyer: an integration surface may remain discoverable long after onboarding and support have ended.
A controlled evaluation workflow
Use the archived material to study a transition rather than to install a new dependency. Teams still referencing Reviewpad configuration should inventory workflows, approval rules and automation that relied on the app. Map each rule to GitHub-native branch protection, current code owner policy or an explicitly maintained replacement. Test that a required reviewer cannot be bypassed after the old bot disappears. Export any accessible historical configuration before changing repository policies.
Limitations and version boundaries
Neither a historical user guide nor the survival of a GitHub listing demonstrates an active commercial service or newly supported API. The acquisition date is a documented corporate event, not an assurance that every prior customer had the same migration path. Reviewpad’s historical automation also must not be conflated with current Snyk products unless Snyk first-party documentation provides a product-specific successor relationship.
Repository security and data governance
Review automation can become a hidden critical control. If an inactive bot formerly labeled sensitive changes or blocked merges, losing it can silently widen approval paths. Audit branch rules and status checks that depend on an unavailable app. Replace required checks deliberately rather than deleting failed statuses just to restore merge flow. Keep a record of when the service was retired and which owners accepted the replacement control.
Who should consider it
The article is appropriate for a 2020–2026 developer-tool history archive or migration checklist, not a “top coding assistant to buy” roundup. A useful historical entry helps users interpret stale screenshots, GitHub Actions manifests and old blog posts without pretending the service is still onboarding new teams.
Alternatives and engineering trade-offs
Current GitHub branch rules, CODEOWNERS, maintained review bots and Snyk’s current offerings must be evaluated separately. None should inherit Reviewpad’s old feature claims or security posture automatically.
Acceptance and reproducibility checklist
- Record the exact installed version, plugin publisher, identity provider, workspace and server/model selection; public documentation may describe a newer build.
- Use a nonproduction repository without real secrets, with fixed acceptance tests and a known starting commit; note the country, tenant and contracted edition.
- Record approval prompts, repository and network permissions, all files changed, commands invoked and failure paths as distinct observations.
- Review source changes and explanations against requirements; run tests, static checks and security scans independently; block unapproved deployment.
- Retain evidence of a human review, rollback and access-revocation plan, and route all unverified price, region and contract items to the responsible owner.
Dates, commercial terms and what remains unknown
This is an editorial snapshot as of 25 October 2026. Scope: historical 2023 acquisition and later maintenance status. Sources below are first-party descriptions and should not be treated as independent hands-on results. Exact plan pricing, seat allowances, general worldwide availability, commercial license guarantees, model IDs and contractual retention terms are not claimed without dated evidence. Where a living documentation page lacks a publication date, this article does not project its features backward. Editorial status is distinct from WordPress publication: the shared import contract has not been checked.
Sources & Further Reading
- https://github.com/reviewpad — first-party source; publication date not established; checked 2026-10-25
- https://docs.reviewpad.com/ — first-party source; publication date not established; checked 2026-10-25
- https://github.com/apps/reviewpad — first-party source; publication date not established; checked 2026-10-25