A clean dashboard means nothing if only one repository is reporting. Coverage answers the other half of the question: where are the checks actually running?
The Coverage page listing repositories with status badges, check counts, branches and domains
Every time the GitHub Action runs against a pull request — pass or fail — it reports back here. This page is built from those reports, so a repository that has never run the Action simply does not appear.

​
Reading a row

​
The status badge

The badge reads latest: pass or latest: fail — it names what it covers, rather than implying a repository is globally healthy.
When the latest check passed but earlier ones failed, an amber “N earlier fails” badge appears alongside. A green badge on a history full of failures would be misleading: it tells you the last commit was clean, not that the repository has been.

​
What to look for

The most important gap on this page is the rows that aren’t there. Coverage can only show repositories that have run the Action — cross-check against your actual repository list.
A repository showing only one feature branch usually means the Action was trialled once and never merged into the default workflow.
A last-checked date weeks old on an active repository means the workflow is failing before the Action runs, or has been removed.
A repository scoped to one domain is only checked against that domain’s statements. Deliberate scoping is fine; accidental scoping looks like compliance and isn’t.

​
Extending coverage

1

Add the Action

Follow GitHub Action to add the workflow to a repository.
2

Run it on the default branch

A workflow that only exists on a feature branch reports once and then stops.
3

Scope deliberately

Omit the domain input to check against every domain, or set it explicitly and record why.
4

Come back here

The repository appears after its first run. If it doesn’t, the Action isn’t reaching the API — check the key and base URL.