All teardowns
sigstore logo

Free Verify scan · sigstore/cosign

cosign scores 64/100

Signing and verification for containers and software artifacts.

Commit 63d9aa1 · 132 controls · Oct 15, 2026 · Re-checked daily

Scanned with public access only. Customer results are never published.

Delivery controls score64
cosign
42median 6886

Out of 100. Stronger than 26% of the 68 other assessed repositories.

Score

64/100

Rank 48 of 69 · median 68

Gaps

33

level with the median of 33

Critical

4 controls

2 root causes

Not visible

24

Needs admin access

What cosign does wellDefault branch identifiedBranch strategy observableDefault branch protected by rulesetVisibility and ownership recordedWork arrives through a tracked path
Gaps33
cosign
15median 3361

Visible controls Verify found unmet. Fewer is better. Stronger than 46% of the 68 other assessed repositories.

How does your team compare?

This is what Canon Verify found in cosign's public configuration. Your team's process probably has the same gaps. Most private repos do.

See how your team scores

5 minutes. No repository access needed.

Scan your own repo with Verify (free)

Analysis

Our read

01

Docs leads the assessment.

5 of 5 visible controls pass in docs.

02

Agents & AI has the most room to improve.

1 visible control remain open in agents & ai.

Priority

Fix these first

critical

Production approvers named

Covers 3 controls
  • Production approvers named
  • Production protection
  • Production reviewers resolved

What Verify read

No resolved production reviewers.

Risk: Unnamed production approvers mean deployment approval falls to whoever is nearby when the button needs pressing.

text
Name production reviewers.

Have this gap too? Start from the PR Review Pipeline flow.

Open in Design
critical

Required checks match workflow names

Covers 4 controls
  • Required checks match workflow names
  • Required status checks strict
  • Required check includes tests
  • Required lint check

What Verify read

Required checks: none

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

Workflow permissions least-privilege

Covers 1 control
  • Workflow permissions least-privilege

What Verify read

One or more workflows do not declare a permissions block.

Risk: Broadly permissioned workflows hand a write token to every action they call, including third-party code.

text
Set least-privilege GITHUB_TOKEN.

Overview

Control map

Public-access limit

24 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.

  • Pull-request requirement on default branchcritical
  • Required reviewscritical
  • Force-push restrictedhigh
  • Administrator bypass restrictedhigh
  • Tag protectionhigh
  • CODEOWNERS reviews requiredhigh
  • Stale reviews dismissedhigh
  • Last-push approval requiredhigh
  • Self-merge restrictedhigh
  • Bypass actors justifiedhigh
  • Push protection enabledhigh
  • Dependabot alertshigh
  • Secret scanning alertshigh
  • SAST required on default branchhigh
  • Environment secrets scopedhigh
  • Signed commits requiredmedium
  • Branch deletion protectedmedium
  • Conversation resolution requiredmedium
  • Merge queue or serialized mergemedium
  • Secret custodiansmedium
  • Audit of privileged actionsmedium
  • Linear history or documented merge methodlow
  • Private vulnerability reportinglow
  • Wait timer or freeze windowlow
Get Verify

Method

How Verify works

01

Read

Verify reads the repository at a pinned commit: settings, rulesets, workflows, and files.

02

Judge

Each control is checked against a written expectation. Same inspector, same criteria, every repository.

03

Prove

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 scanVerify on your repository
AccessPublicGitHub App you install
Controls read92 of 92All 92
Private repositoriesNoYes
ResultsPublished herePrivate to your organization

Evidence locker

Every control Verify checked

Governance

4 of 12 pass

Review

11 of 26 pass

CI & tests

20 of 30 pass

Code quality

2 of 8 pass

Security

10 of 20 pass

Agents & AI

0 of 8 pass

Release & ops

7 of 22 pass

Assessment timeline

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.

Sep 21 · 64Oct 15 · 64

Nothing has changed since Canon started recording this repository.

Get this report for your own repository.

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 →

View sigstore/cosign on GitHub

Maintain cosign? If anything here is inaccurate or out of date, email security@strikelabs.co and we'll correct it.