Scanned with public access only. Customer results are never published.
Delivery controls score71
next.js
42median 6886
Out of 100. Stronger than 63% of the 68 other assessed repositories.
Score
71/100
Rank 24 of 69 · median 68
Gaps
31
2 fewer than the median of 33
Critical
0 controls
0 root causes
Not visible
15
Needs admin access
What next.js does wellDefault branch identifiedBranch strategy observableDefault branch protected by rulesetForce-push restrictedPull-request requirement on default branch
Gaps31
next.js
15median 3361
Visible controls Verify found unmet. Fewer is better. Stronger than 56% of the 68 other assessed repositories.
How does your team compare?
This is what Canon Verify found in next.js's public configuration. Your team's process probably has the same gaps. Most private repos do.
Risk: Approvals that survive a new push mean the merged code is not the code anyone approved.
text
Dismiss stale reviews.
high
Last-push approval required
Covers 1 control
Last-push approval required
What Verify read
Last-push approval: false
Risk: A final push after approval can introduce anything, and the merge still shows a green review.
text
Require last-push approval.
Overview
Control map
Public-access limit
15 controls this scan couldn't read
This free scan used public access only. These controls live in settings only a repository admin can read. Verify checks them on your connected repository.
