devwithcoffee

Killed by Me

Every side project you abandoned on GitHub, finally given the funeral it never got. Type a username — yours, a friend’s, your favourite maintainer’s.

orSign in with GitHubto include your private repos — read-only, names hidden

Even legends leave bodies

Everyone who ships abandons far more than they ship. A snapshot of some well-known graveyards, taken 2026-09-23 — public repos, plus private ones where someone has added their own. Click a name for the live version.

WhoKilledMedian lifeVerdict
Linus Torvalds@torvalds3 / 912 monthsThe Gardener
Himanshu Srivastava@himanshuSri2466 / 101incl. 67 privateless than a dayThe Necromancer
dan@gaearon53 / 618 monthsThe Long Goodbye
Sindre Sorhus@sindresorhus501 / 9908 yearsThe Necromancer
Andrej@karpathy44 / 5414 monthsThe Long Goodbye
Salvatore Sanfilippo@antirez79 / 1023 weeksThe Gravedigger
TJ@tj214 / 21923 monthsThe Long Goodbye
Evan You@yyx99080374 / 753 monthsThe Long Goodbye
levelsio@levelsio0 / 24 monthsThe Cautious
Kent C. Dodds@kentcdodds375 / 4033 yearsThe Long Goodbye
Mitchell Hashimoto@mitchellh97 / 10615 monthsThe Long Goodbye
shadcn@shadcn143 / 1491 dayMass Extinction Event
ThePrimeagen@ThePrimeagen176 / 1949 daysThe Gravedigger
Theo Browne@t3dotgg95 / 1022 daysMass Extinction Event
Addy Osmani@addyosmani161 / 18511 daysThe Gravedigger
Guillermo Rauch@rauchg57 / 652 monthsThe Gravedigger
Kyle Simpson@getify65 / 7116 monthsThe Long Goodbye

Why this exists

I scanned every project on my own disk and found the median one lived nine days. My public GitHub is worse: the median repo lasted two days, and fifteen of them died the day they were created. I don’t think that’s a character flaw. Most side projects are questions, and most questions get answered in a weekend.

But it is funny, and it turns out almost everyone who ships a lot has the same graveyard. The difference is only whether anyone counts. So now anyone can.

Frequently asked

What counts as a dead project?

A public repository you created that has not had a push in over a year. No push in three months counts as dying. Archived repos are counted as properly buried, and forks are left out entirely — you can't kill something that was never yours.

Is my data stored or sent anywhere?

For public repos, no. Your browser asks GitHub's public API for the list and does all the counting itself; this site never sees the request. The only thing ever stored is the anonymous private-repo summary described below, and only if you sign in and ask for it.

How do private repos stay private?

Signing in installs a GitHub App whose only permission is read-only repository metadata, so it cannot read a line of code. The server reads your repo list once, keeps just the dates, language, size and a few counts for each private repo, and revokes the sign-in token immediately. Names, descriptions and topics are thrown away, so on your page and your share card they appear only as 'Private project #7'. Remove them any time from your page, and uninstall the app from GitHub's settings if you want it gone entirely.

Why does it say GitHub's limit is used up?

GitHub allows 60 unauthenticated requests an hour per network. One graveyard costs two requests for most people, a few more for someone with hundreds of repos. On a shared office or university network other people may have spent the allowance; it resets within the hour.

How is the lifespan measured?

From the moment the repository was created to its most recent push. The median is the middle value across all your repos, so a single long-running project can't hide a hundred abandoned ones — which is exactly why the number is uncomfortable.

Are the epitaphs random?

No. Each one is chosen from what is true about the repository — how long it lived, whether it had a description, its stars, its open issues, its name — and the same repository always gets the same one.


Built by Himanshu Srivastava — verdict: Serial Starter. This one he intends to keep alive. Inspired, with love, by Killed by Google. More in the tools collection.