A year of GitHub contributions across the United States, drawn as a spinning tornado: all 50 states, the nine Census divisions and four regions, every county in the country on a map, and leaderboards in eight categories. About 34,000 developers found, the likeliest-busiest 80 in each state compared, refreshed every day by GitHub Actions. One HTML page and the shapes of the counties, no frameworks, no dependencies, and nothing loaded from anywhere else.
See it live: https://wbp318.github.io/github-leaderboard/ and type your GitHub login to see where you rank. Not on it? One click adds you.
Tip
Runs best in Chromium. The tornado is a live canvas animation, and it is at its smoothest in Chromium and the browsers built on it (Chrome, Edge, Brave, Arc, Opera, Vivaldi). Firefox and Safari work too, just not as smoothly.
- Windows:
winget install Hibbiki.Chromium. This community build never updates itself, so keep it current: runwinget upgrade Hibbiki.Chromiumevery few days, or have Windows check daily for you (below). - macOS: with Homebrew,
brew install --cask ungoogled-chromium(Chromium without Google's services). Homebrew's plainchromiumpackage was retired in September 2026 because Apple's security check rejects it. If macOS will not open the app the first time, go to System Settings → Privacy & Security and choose Open Anyway. Homebrew does not update it on its own either: runbrew upgrade --cask ungoogled-chromiumnow and then. Or use Google Chrome, which updates itself:brew install --cask google-chrome. - Linux:
sudo snap install chromium(snaps update themselves), or your distribution'schromiumpackage.
Have Windows update Chromium every day
Paste this into PowerShell once. It adds a task that runs winget upgrade for Chromium every morning at 9 (or as soon as the PC is next on), hidden, as you, with no administrator rights needed. The last run's output is in %LOCALAPPDATA%\chromium-update.log.
$log = Join-Path $env:LOCALAPPDATA "chromium-update.log"
$run = "winget upgrade --id Hibbiki.Chromium --exact --silent --accept-source-agreements --accept-package-agreements > `"$log`" 2>&1"
Register-ScheduledTask -TaskName "Update Chromium" -Force `
-Action (New-ScheduledTaskAction -Execute "conhost.exe" -Argument "--headless cmd.exe /c $run") `
-Trigger (New-ScheduledTaskTrigger -Daily -At 9am) `
-Settings (New-ScheduledTaskSettingsSet -StartWhenAvailable -AllowStartIfOnBatteries -DontStopIfGoingOnBatteries)To stop it: Unregister-ScheduledTask -TaskName "Update Chromium".
-
Every county, on a map. First on the page, under the header: all 3,141 counties in the 50 states, coloured by contributions, people counted, or average. Click a state to zoom in, and a county to see its leaderboard; arrow keys, Enter, and Escape do the same. Get closer with the + and − buttons, the mouse wheel, or a pinch, and drag to move around. Tab to it and a gold outline, with a note saying what it is, moves between states and counties with the arrow keys. People are placed in a county by the town, city, university, or county named in their GitHub location, from the Census Bureau's lists of places, and where those leave a gap, from every post office (as USPS names it) and unincorporated community, so Sondheimer, Louisiana is East Carroll Parish.
-
Ice Storm. Under the map, arcade hockey the way the 16-bit games played it, five on five: the storm froze the rink. The fourteen teams carry the names of clubs from the old Western Professional Hockey League (1996–2001), in the league's colours for them: the Monroe Moccasins, Tupelo T-Rex, Lake Charles Ice Pirates, Alexandria Warthogs, Arkansas GlacierCats, Abilene Aviators, Amarillo Rattlers, Central Texas Stampede, El Paso Buzzards, Fort Worth Brahmas, Lubbock Cotton Kings, New Mexico Scorpions, San Angelo Outlaws, and Waco Wizards. Their crests are new, drawn in code with what the old ones showed (a T-Rex with a stick in its teeth, a cotton boll in a crown), and none is a copy. You're the home team, in white, as home teams wore then. Skate; pass to the teammate the way you're skating; tap shoot for a wrist shot or hold it for a slapshot, pushing up or down to pick a side of the net; shoot as a pass arrives for a one-timer; and without the puck, check, or switch to whoever's nearest it. Win a faceoff by pressing as the puck lands. Three periods of two, three, or five minutes, sudden-death overtime, and Rookie, Pro, or All-Star, with your record kept in your browser. It's seen from up in the stands, the ice drawn in perspective the way the old consoles drew a floor, with a crowd that jumps on a goal, the goal light, the horn, and an arena organ playing riffs written for it (N or the Organ switch turns it off). Play it with the keyboard, a phone's touch pad, or a game controller (an Xbox one, by USB or Bluetooth: connecting it); Keys, under the game, changes any key or button. The hockey itself, the skating, the puck, the computer's players and goalies, and the rules, is src/hockey.mjs, and the tests play whole games with it. It only runs while you play, and links to a view or to someone's ranks open past it.
-
The tornado. Each ring is a place, the busiest at the top. Its red half is public commits; its blue half is everything else: pull requests, reviews, issues, new repositories, and private contributions for people who show them. Click a ring to go down a level, from divisions to states to a state's busiest people. Every state by county has a tornado of its own (Louisiana by parish, Alaska by borough), the 24 busiest counties a ring each and the rest together. It works from the keyboard too: Tab to it, arrow keys to move between rings, Enter to go down, Escape to come back up. A screen reader reads each ring's place and numbers. Round it the weather rolls in: clouds, rain, debris riding the updraft, and every few seconds lightning that strikes the busiest ring, with thunder if you turn it on. The Storm switch turns it all off, and it starts off if your system asks for reduced motion.
-
Find yourself. Type your GitHub login to see your ranks in your parish or county, state, division, region, and the country, with you in gold in the tornado, the lists, and the map.
?me=<login>links straight to anyone's ranks. Open any other state to see where you would rank there, and the states table shows your rank in all 50 at once. -
Share your ranks. Once you've found yourself, Share my ranks draws a picture to post: your GitHub picture, your year, your ranks from county to country, and your state's tornado with you in gold. Download it, copy it, or share it straight from a phone. It also hands you a badge for your profile README, which the daily build redraws, so it always shows today's rank:
-
Add yourself. Not on it? The Add me button opens a one-click issue; a bot checks your profile location, adds you, and replies with a link to your ranks in a few minutes. You are refreshed daily after that.
-
Leaderboards in eight categories (total, public commits, private, pull requests, reviews, issues, new repositories, followers) for any state, division, region, or county, with each person's location. Search by login, name, or place. Download CSV saves the list as you have it, every row and every category, for Excel or Google Sheets.
-
A tile map of the 50 states, coloured the same ways.
-
Tables of the states, the regions and divisions, and each state's counties.
-
Music, and the page moving to it. Play music, at the top, plays three original, upbeat techno tracks made in code ("Storm Warning", "Flood Stage", and "Supercell"), one after another, with Next and a volume that's remembered. The page moves with it: a spectrum along the top edge in the tornado's red and blue, the title and a glow pulsing on every kick, the tornado's rings swelling to the beat, lightning striking on each drop, and a gold flash round the edges when a chorus hits. It waits while you play Ice Storm, which has its own organ, and nothing moves if your system asks for reduced motion.
-
Light or dark. The page follows your system's setting; the switch at the top changes it and remembers your choice.
-
History. In the states table, a small line for each state shows how its contributions have moved since the history started. Open a state's tornado for a chart of its total, day by day.
flowchart TD
search["GitHub search<br/>users whose location names each state,<br/>by followers and by repositories"] --> cands[("candidates")]
cands --> prof["GitHub GraphQL<br/>location, followers, public repos, last push"]
prof --> place{"src/states.mjs<br/>which state, if any?"}
place -->|"pushed in the last year:<br/>the likeliest 80 a state,<br/>everyone in LA, MS, AL, AR, and TN"| contrib["GitHub GraphQL<br/>a year of contributions"]
contrib --> audit["scripts/audit.mjs<br/>what each rule placed and turned away"]
audit --> build["scripts/build.mjs<br/>states, divisions, regions, parishes and counties, rankings"]
build --> page["site/leaderboard.html<br/>published to GitHub Pages"]
daily(["GitHub Actions, every day"]) -.-> search
daily -.-> page
- Find people. scripts/collect.mjs searches GitHub for users whose location names each state, by its name and by its two-letter code, and Louisiana again by its towns.
- Place them. src/states.mjs reads each free-text location. Two-letter codes are shared around the world (MS is also Mato Grosso do Sul in Brazil, DE is Germany, IN is India, WA is Western Australia), so a code only counts when the city in front of it is not a known place abroad that uses the same code. Louisiana goes down to the parish, and Mississippi, Alabama, Arkansas, and Tennessee to the county, with src/counties.mjs, and a few town names that mean only one of them ("New Orleans", "Hattiesburg", "Tuscaloosa", "Little Rock", "Chattanooga") place someone there without the state. docs/placement.md explains the rules, and the tests hold the hard cases.
- Look up contributions. For each state, the 80 people most likely to be busiest (by public repositories and followers, among those who pushed code in the last year) get their year of contributions looked up. Everyone else active is looked up once a week (up to 1,000 a state), for the parish and county views. States are always compared on the same 80 each. The busiest accounts are too big for GitHub to count in one query, so they are counted the long way rather than dropped; bot and test accounts are left off.
- Audit and build. scripts/audit.mjs lists what each rule placed and what it turned away; scripts/build.mjs adds everything up and writes it into web/template.html.
- Every day at about 4:23 a.m. Central, a GitHub Actions workflow refreshes what has gone stale (contributions daily, searches and profiles weekly), adds the day's numbers for each state to a small history (scripts/history.mjs), saves the data to the
databranch, audits it, and publishes the page. GitHub starts scheduled workflows late, sometimes hours late, and sometimes not at all, so the workflow is triggered every hour and the first trigger after 4:23 refreshes (scripts/refresh-due.mjs); the rest stop in seconds. As a fallback outside GitHub, a Windows task on my PC (scripts/refresh-fallback.ps1) starts it if that hasn't happened by 7:30. If a refresh is late, the top of the page says so, and reloads itself when it lands. It uses the workflow's own token, so there are no secrets. docs/data.md describes every file.
Node 24, no dependencies.
npm run data # download the latest data
npm run build # write site/leaderboard.html
npm test # the placement rules
npm run audit # data/audit.mdTo collect from GitHub yourself (about an hour for every state), see CONTRIBUTING.md.
src/ placement rules: states.mjs, counties.mjs, counties/ (us.json, aliases, 5 hand-made states), opt-out.txt; badge.mjs, geo.mjs (decodes the county map)
scripts/ collect, audit, build, fetch-data
web/ template.html, the whole page; us-counties.json, the county map's shapes
site/ what GitHub Pages serves (leaderboard.html, us-counties.js, and badge/ are built; index.html and social.png, the picture a shared link shows, are kept here)
test/ placement test cases
docs/ placement.md, data.md, the screenshots
.github/ the daily workflow, issue forms
- How people are placed: the shared two-letter codes, the rules, the audit, and how to fix a mistake.
- The data: every file, every field, how it is collected, and the settings.
- Contributing: running it, where to start, and ideas to pick up.
- Contributions are GitHub's own count for the last 12 months, the number on a profile's contribution calendar.
- Private contributions count only for people who choose to show them on their profile.
- It is a sample, not a census. In each state the 80 people looked up are the likeliest to be busiest by their public signals, so someone very active who works mostly in private can be missed. Ranks are among the people counted.
- People are placed by what their profile says. Locations that stay ambiguous (Georgia the country, Washington DC, two places at once) are left out, and so are bot and test accounts.
- It changes daily. Contribution counts cover a rolling 12 months, so ranks move a little every day.
Ideas, fixes, and new views are welcome; CONTRIBUTING.md has how to run it, where things are, and ideas to pick up, and the code of conduct keeps it friendly. Someone in the wrong state? Tell me.
Everything shown comes from public GitHub profiles. To be left off, add your login to src/opt-out.txt or open an issue.
The county places come from the U.S. Census Bureau, the USGS's Geographic Names Information System (public domain), and GeoNames' US postal codes (CC BY 4.0), through scripts/make-counties.mjs.


