Scanned with public access only. Customer results are never published.
Delivery controls score62
react
42median 6886
Out of 100. Stronger than 21% of the 68 other assessed repositories.
Score
62/100
Rank 53 of 69 · median 68
Gaps
40
7 more than the median of 33
Critical
4 controls
2 root causes
Not visible
15
Needs admin access
What react does wellDefault branch identifiedBranch strategy observableDefault branch protected by rulesetForce-push restrictedPull-request requirement on default branch
Gaps40
react
15median 3361
Visible controls Verify found unmet. Fewer is better. Stronger than 18% of the 68 other assessed repositories.
How does your team compare?
This is what Canon Verify found in react's public configuration. Your team's process probably has the same gaps. Most private repos do.
Risk: If required checks do not match the jobs that run, a rule appears to protect the branch while enforcing nothing.
text
Align required checks with jobs.
high
CODEOWNERS or review assignment
Covers 4 controls
CODEOWNERS or review assignment
CODEOWNERS or OWNERS file
Maintainer roster
Review of high-risk dependency changes
What Verify read
No tree evidence for owners.
Risk: With no ownership file, review lands on whoever is available rather than whoever understands the code.
text
Add CODEOWNERS.
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.
