Governance leads the assessment.
9 of 10 visible controls pass in governance.

Free Verify scan · ossf/scorecard
Automated security health checks for open-source projects.
Commit a1fe90a · 132 controls · Oct 15, 2026 · Re-checked daily
Scanned with public access only. Customer results are never published.
Out of 100. Stronger than 60% of the 68 other assessed repositories.
Score
70/100
Rank 27 of 69 · median 68
Gaps
31
2 fewer than the median of 33
Critical
3 controls
1 root cause
Not visible
13
Needs admin access
Visible controls Verify found unmet. Fewer is better. Stronger than 56% of the 68 other assessed repositories.
This is what Canon Verify found in scorecard's public configuration. Your team's process probably has the same gaps. Most private repos do.
5 minutes. No repository access needed.
Analysis
9 of 10 visible controls pass in governance.
1 visible control remain open in agents & ai.
Priority
What Verify read
No resolved production reviewers.
Risk: Unnamed production approvers mean deployment approval falls to whoever is nearby when the button needs pressing.
Name production reviewers.Have this gap too? Start from the PR Review Pipeline flow.
Open in DesignWhat Verify read
Code-owner reviews: false
Risk: Without required code-owner review, a change to a sensitive area can be approved by someone unfamiliar with it.
Require code-owner review.What Verify read
Dismiss stale: false
Risk: Approvals that survive a new push mean the merged code is not the code anyone approved.
Dismiss stale reviews.Overview
Public-access limit
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.
Method
01
Verify reads the repository at a pinned commit: settings, rulesets, workflows, and files.
02
Each control is checked against a written expectation. Same inspector, same criteria, every repository.
03
Every result shows the evidence Verify read. Assessments re-run daily, and changes are logged.
132 controls · 69 repositories assessed · re-run daily
| This free scan | Verify on your repository | |
|---|---|---|
| Access | Public | GitHub App you install |
| Controls read | 103 of 103 | All 103 |
| Private repositories | No | Yes |
| Results | Published here | Private to your organization |
Evidence locker
Canon re-assesses this repository daily. An entry appears only when something changed — the score, a control's outcome, or a control ceasing to apply.
Canon Verify runs the same inspection on your private repo. Read-only GitHub App. First scan free.
Read-only access. No code stored. How Canon handles your data →
Maintain scorecard? If anything here is inaccurate or out of date, email security@strikelabs.co and we'll correct it.