Scraping repos…
Reading their public GitHub…
Arif Nurdiansyah
@arifnurdiansyah92 · public profileROASTED
31/100
🔥 D-TIER DISASTER
“50 repos and 17 stars, but 37 of them haven't been touched in over a year.”
DRank tierD-tier Tutorial Graduate
Mint vaultArtifact · @arifnurdiansyah92
Roast style
GITROAST.ME
Minted from @arifnurdiansyah92’s public GitHub
7followers17stars50reposPHPtop lang
Why 31/100
- Impact2.8/32
Stars on your live, original repos — discounted if it's all one viral hit.
- Community1/10
Developers who follow your work.
- Consistency4.3/14
How much of your live portfolio is actually active.
- Portfolio12.6/15
Substantive original repos and language range.
- Craft2.5/10
Descriptions, licenses, topics, live links — finished work.
- Recency2/5
Days since your last push to a live original repo.
The roast
You’ve got 50 repos, yet 47% of them are so empty they might as well come with a ‘content not found’ message. Abandoned by their creator, 35 have been left to die within two weeks, and you’ve let the open issues pile up to 19 in musicool — a real masterpiece of neglect. A staggering 16 repos weigh in under 20 KB each, almost like you were aiming for a participation trophy rather than any semblance of production.
Your star distribution screams vanity: 13 out of your total 17 stars come from AbsenSiswa alone, while the rest are scattered like you're throwing darts in the dark. Nine languages across 43 original repos just illustrate your indecision, while every other language sits collecting dust — clearly coding in your free time still translates to filing more abandonment notices than real work. With a Builder Score of 31/100, it seems like your only consistent output is letting potential projects rot.
The flex
Your GitHub, as a badge.
[](https://gitroast.me/u/arifnurdiansyah92)
