Methodology

DevImprint measures one narrow thing: commits published in public repositories that carry a detectable signature from an AI coding tool. It is not a measure of productivity, effort, seniority, or code quality, and it cannot see private work.

What counts as an AI-assisted commit

A commit is attributed to a tool when it carries at least one of four signals. Each tool's exact patterns are listed on its own page.

1. A co-author trailer. Many tools append a Co-Authored-By: line with an address they control, for example [email protected]. This is the strongest and most common signal.
2. A bot author address. Some agents commit as themselves rather than as a co-author, using a fixed address such as [email protected].
3. A bot author name. GitHub Apps commit under a deterministic name[bot] form, for example devin-ai-integration[bot].
4. A message-body pattern. A few tools write a fixed line into the message, such asGenerated with Claude Code.

Signals are matched case-insensitively and anchored where the pattern is deterministic, so a near miss fails to match rather than attributing the commit to the wrong tool. A commit may carry more than one signal and is then credited to every tool it names.

The ranking window

The rank is the count of AI-assisted commits authored in the trailing 30 days, currently the window beginning 2026-08-09. Lifetime totals are shown alongside but do not affect rank, so the board reflects current activity rather than accumulated history. Ties are broken toward more recent activity.

Who appears

Rows are people with a public identity. Two categories are removed before anything is published:

• Email-shaped identities. When commit history yields only an address and no resolved account, the row is dropped rather than published. Publishing an address that a person did not choose to display is not something a ranking justifies.
• Tools and automation. Bot accounts are the thing being measured, not participants in the ranking. A commit authored by copilot[bot] counts toward that tool's totals and toward the repository, never toward a person.

The site builds 846 profile pages, one for each person in the published ranking. Tools and unresolved identities have no profile: there is nothing behind the name to show.

Unresolved identities

Not every commit can be traced to an account. When history yields only an address, that row is ranked and counted but published as an opaque handle such as unresolved-a1b2c3d4e5f6, never as the address itself. The address is real data, and republishing it on a ranked page would disclose something its owner never chose to display, so it stops at the pipeline. The handle is stable, so the same identity keeps the same label between snapshots and you can watch it resolve.

There are more of these than you might expect. In the current snapshot roughly half of all ranked entries are not a person: some are tools committing under their own identity, the rest are unresolved. You can show either group using the filter above the leaderboard.

They are also not who you would guess. Measuring contributor linkage across the ranked repositories, an identity is about twenty times less likely to be unresolvable on a repository with a single contributor than on one with several. Unresolved identities are concentrated in large, long-lived, many-contributor repositories, which is the signature of imported and vendored history, merged forks, and commits authored under addresses never registered to an account. Most of them are not developers we could ask; they are history the repository inherited.

What the method cannot see

• Private and internal repositories. Nothing outside public history is read.
• Work where the developer turned tool attribution off, which many people do.
• Commits squashed or rebased by someone else, which usually drops the trailer.
• Tools that leave no signature at all, including most inline completion.
• Repositories that have not yet been scanned. See coverage.

Every one of these pushes counts down. Treat a number here as a floor on detectable AI-assisted work, never as a total.

Provenance

Each published snapshot carries the digest of the artifact it was produced from, the time it was generated, and the coverage that stood at that moment. The current snapshot is4960583d05fc666c, generated 7 Sept 2026, 08:12 UTC. The same document that backs these pages is downloadable at /leaderboard.json.

Tools detected in the current snapshot: Aider, Blackbox, Claude Code, Codeium, Codestral, Codex, Cody, Continue, Copilot, Cubic, Cursor, Devin, Jules, Netlify Coding, Openhands, Replit, Sweep, Windsurf.

Opting out

Anyone can ask to be removed. A removal takes effect on the next build and covers the leaderboard, the profile page, the downloadable document, and the social card; the profile URL then returns a permanent “gone” response rather than a redirect. Aggregate counts retain the commits without the identity attached.

A self-serve control arrives with profile claiming. Until then, removal requests go to[email protected] from an address or account that can be matched to the profile.

Corrections

If a number here is wrong, the fix and the reason are published rather than quietly applied. Attribution errors are the most likely kind: a shared address, an unusual bot name, or a tool that changed its trailer. Reports are welcome at the same address.