The radar
Each point is where @AIMLPM ranks, over the same days, among more than 2,500 of GitHub's most active builders, many of them leading agent-orchestration developers, so a high rank here is harder to earn than on a typical leaderboard. The outer edge of the spider chart below is first place: the elite of the elite.
The right half is Volume, the left half is Consistency; tap either to jump to its section.
Tap any axis for the count behind it.
Volume
The newest stretch of 30 active days ran at 213.4 contributions a day, 3.1× their earlier pace of 69.9.
Pace, in stretches of 30 active days
GitHub recordHow it's measured
Substantive commits per active day
iD8 countedPeak day · their ten busiest days
GitHub recordConsistency
In the last 30 days, 29 were solid days (10 or more contributions) and 24 reached 50.
Every day of the year, in the radar's own tiers
GitHub recordHow it's measured
- Active day
- A day with at least one GitHub contribution: a commit, pull request, review or issue, private ones included when the profile shares them.
- Solid day
- A day with 10 or more contributions.
- 50+ day
- A day with 50 or more, drawn in the three brightest shades.
- Solid streak
- The most solid days in a row. Outlined in red.
- Active streak
- The most active days in a row. Any contribution counts, so it can run longer than the solid streak.
The shades are the same for everyone, so two people's calendars compare directly. Days are UTC calendar days.
Stamina
iD8 counted
Read from their own repositories by the iD8 count, which they ran in their GitHub account; private repositories never leave it. Only people who ran it have these figures, so they are not ranked. How the count works
The longest run with a substantive commit in every hour lasted 75 hours, from 30 Sep 09:06 to 3 Oct 12:08 (America/Los_Angeles).
Times are @AIMLPM's local time zone (America/Los_Angeles).
Long days
Time of day · share of substantive commits
How it's measured
iD8 counted counted through 7 Nov 2026 · 30 repositories, 24 private · refresh your count →
Substantive means every commit they authored on a repository's default branch, except merges, automated commits (messages that start with chore, ci, release, a version number and the like) and placeholder messages such as "wip", "fix" or ".".
The record
Monthly contributions · last 24 months, public and private
Per year · and the year before the last 365 days
Size · median lines per substantive commit
What they see in their count · the run of 8 Nov 2026
The totals of their count run of 8 Nov 2026, from 30 repositories, 24 of them private.
How to read the signals
Contributions come from GitHub's own calendar: commits, pull requests, reviews and issues, as GitHub counts them. Private work is in the total when the profile shares it. Calendar days are UTC.
A change in pace says more than a total. Pace compares the newest stretch of 30 active days with the person's own earlier pace, so a jump shows when their output changed.
Public commit counts are floors. GitHub's public records break down public repositories only, so anyone with private work has done more than they show.
No private contributions is not a quiet profile. Much of the busiest work sits in companies' private repositories, and sharing private counts is each person's choice.
iD8 counted figures come from the person's own count, run in their GitHub account: every commit they authored on each repository's default branch, sorted into substantive, merge, automated and micro by the first line of its message. Private repositories are read inside their account, and their names never leave it.