The percentage of pull requests that were merged without review. If the author of a PR merges it without any comments or approvals, it's considered unreviewed.

Unreviewed pull requests can present a risk to your codebase. In the short term, the review process is often the final opportunity to catch mistakes before the pull request is merged. Over the long term, the review process ensures knowledge sharing across the engineering team.

If leaving some pull requests out of the review process is intentional, take care to ensure that the pull requests left unreviewed are matching your expectations. If Unreviewed PRs is higher than you expected, consider automating enforcement of code reviews on repositories with code shipped to production.

The median organization merges 11% of PRs without review. A quarter of organizations merge less than 4% of PRs without review, while, at the other extreme, a quarter merge at least 26% of PRs without review.