Source: GitHub GraphQL contribution calendar (public + opted-in private counts) · commit history on each person's top public repos · git author timestamps for local hours.
The badge
This page is generated from GitHub's records by the radar pipeline; nothing on it is typed in.
Step change beats total. The calendar counts commits, PRs, reviews, and issues, and a PR plus its commits count several times. Maintainers of large projects carry review and issue volume that is fame, not throughput. The unlock shows as a break in slope, a jump in per-active-day, and a rising count of days over 50.
Agent trailers are the direct evidence, with a blind spot. Claude Code writes a Co-Authored-By trailer by default. Cursor, Codex, Copilot, and Google's tools mostly do not, so a zero here is not proof of hand-typed commits. A zero sitting beside a dozen AGENTS.md files in the same account is the ordinary case.
Harness files show intent. CLAUDE.md, AGENTS.md, .cursorrules, and copilot-instructions.md in someone's public repos mean they have configured agents, whatever the commit messages say.
Local hours separate pipelines from people. Git keeps the author's own timezone offset even though GitHub's API strips it. A high share of commits between 22:00 and 06:00 local, or a flat 24-hour spread, is the "while I sleep" signature.
Commit counts from the API are public-only. The calendar total includes opted-in private work, but the commit breakdown does not, so commits per active day is a floor for anyone whose private counts run into the thousands. A row marked † is GitHub-served from that person's own repositories, private ones included, read from GitHub's copy and deduplicated by SHA, so it is the full figure and anyone granted read access can reproduce it.
Private counts are opt-in. A profile that shows none is not evidence of low output. High-output work often sits in a company's private repositories, or in an organisation the API will not expose at all.