Scraping repos…
Reading their public GitHub…
🔥 C-LEVEL DISASTER
“C-LEVEL DISASTER ON GITHUB”
Tap the card to see how it was minted
Minted from @angeluriot’s public GitHub
751followers881stars41reposC++top lang
Why 58/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
Your repo count screams quantity over quality with 41 repos and only 17% seeing any action in the last 90 days. "Chess_games" abandoned in just two weeks, a haunting testament to your lack of commitment. The naming blunders in "Portfolio" and "Sandbox" showcase a creativity drought that even a bored intern wouldn’t tolerate.
The gravitas of your top repo, 'Galaxy_simulation,' hides behind its 210 stars while the rest stall in mediocrity. C++ takes the crown with 393 stars, but the longest gap between pushes at 146 days proves you’re more of a hit-and-run developer than a dedicated builder. With a Builder Score of 58/100, you might want to rethink the concept of a work in progress—maybe aim for a work in existence instead.
[](https://gitroast.me/u/angeluriot)Account age, portfolio size, public repo count.
Builder Score recalibrated 2026-07.