Scraping repos…
Reading their public GitHub…
🔥 C-TIER DISASTER
“35 repos dead on arrival—your idea of clean architecture is a clean graveyard.”
Tap the card to see how it was minted
Minted from @khannedy’s public GitHub
4.1Kfollowers1.8Kstars45reposJavatop lang
Why 43/100
Stars on your live, original repos — discounted if it's all one viral hit.
Developers who follow your work.
How much of your live portfolio is actually active.
Substantive original repos and language range.
Descriptions, licenses, topics, live links — finished work.
Days since your last push to a live original repo.
The roast
You’ve got 35 repos like eMovieRental and ePhoneBook that died in under two weeks and have been silent for over six months. With a push cadence featuring a staggering 835 days of inactivity, your coding output is more haunted than productive. Your latest push was in 2025, while you cling to 42 untouched repos, leaving an impressive pile of open issues, including 18 languishing on notes.
Tracking a grand total of 1822 stars, your top projects revolve around Go and Shell, yet somehow you’ve managed to not archive a single project — a fittingly bold choice for someone with zero momentum. With a Builder Score of 43/100, calling you a “work in progress” is generous at best; it’s just a tombstone marking where innovation goes to rot. You should consider giving your repos the dignity of a proper burial, rather than letting them decompose under a facade of activity.
[](https://gitroast.me/u/khannedy)Account age, portfolio size, public repo count.
Builder Score recalibrated 2026-07.