Scraping repos…
Reading their public GitHub…
🔥 CERTIFIED DISASTER
“48 repos and only 17 stars? Even a ghost gets more attention.”
Tap the card to see how it was minted
Minted from @arifnurdiansyah92’s public GitHub
7followers17stars48reposPHPtop lang
Why 31/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 have 31 repos untouched for over a year, yet you still call yourself a developer. AbsenSiswa has 13 stars, while the remaining 40 repos barely scrape together 4; your star-to-repo ratio is an embarrassing 0.38. A shocking 46% of your original repos come with zero descriptions — did you think they’d describe themselves?
You’ve got 16 repos under 20 KB — that’s more like a landfill than a portfolio. Creating 35 repos just to abandon them within two weeks shows your commitment to nowhere; projects like Hotel and ANFramework are just ghosts of ambition. With a D-tier Builder Score of 31, it’s clear you’ve mastered the art of collecting repos while actively ignoring the code. Time to reconcile that profile with some actual work, or just accept that your repo graveyard is at risk of becoming a national park.
[](https://gitroast.me/u/arifnurdiansyah92)Account age, portfolio size, public repo count.
Builder Score recalibrated 2026-07.