DevImprint.

Coverage

Rankings are only as complete as the scan behind them. This page states exactly how complete that is right now, and it is generated from the same snapshot as every other number on the site.

Rankings are provisional. They stay marked this way until at least 100% of known repositories have completed a scan. Today that figure is 33.2%.

What this means for a number on this site

A developer's count includes only commits from repositories that have completed a scan. If someone's main repository is still queued, some activity is missing. Attribution errors can also inflate counts, so the observations are neither verified totals nor guaranteed lower bounds.

Coverage rises continuously as the scan proceeds, so a rank is a statement about a moment, not a verdict. Comparing two developers is only fair when both have similar coverage, which the site cannot yet report per person.

Scanned versus inherited

Two different populations are reported separately on purpose, because conflating them would inflate every figure.

Scanned in this cycleInherited index
Repositories1,074,9963,201,705
Developers1,050,4206,630,108
Commits123,983,143 AI-assisted6,089,060,370 all kinds

The inherited index is the catalogue of repositories and identities carried over from the previous generation of the pipeline. It describes what is known to exist, not what has been measured. Only the scanned column backs a ranking.

Archived corpus parity

Archived corpus parity counts how many of the same 100 identities in the inherited 2026-08-03 corpus have been rebuilt to at least their archived 30-day and lifetime AI-assisted commit counts after current identity resolution. It does not compare their old ranks or display names. This measures historical rebuilding progress, separate from today’s repository scan share and the current leaderboard.

No published parity measurement. The matched count is unavailable, not zero.

The observation time belongs to this parity check. A newer leaderboard snapshot does not make an older parity observation new.

This snapshot

The pages and the current document are published together. Figures reflect the source snapshot shown above and do not update between deployments. Retain the digest with any exported data so the observation remains identifiable after the next publication.