Scanned with public access only. Customer results are never published.
Delivery controls score68
node
42median 6886
Out of 100. Stronger than 43% of the 68 other assessed repositories.
Score
68/100
Rank 33 of 69 · median 68
Gaps
35
2 more than the median of 33
Critical
4 controls
2 root causes
Not visible
15
Needs admin access
What node does wellDefault branch identifiedBranch strategy observableDefault branch protected by rulesetPull-request requirement on default branchGitHub App bypass inventory
Gaps35
node
15median 3361
Visible controls Verify found unmet. Fewer is better. Stronger than 34% of the 68 other assessed repositories.
How does your team compare?
This is what Canon Verify found in node'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
Force-push restricted
Covers 1 control
Force-push restricted
What Verify read
Force-push allowed: true
Risk: A force push rewrites shared history, destroying the audit trail and any reviewed commit an incident later depends on.
text
Forbid force-push on main.
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.
