Scraping repos…
Reading their public GitHub…
🔥 GHOST CODER
“Your repo graveyard has more activity than your actual projects.”
Tap the card to see how it was minted
Minted from @ikhsan3adi’s public GitHub
593followers1.1Kstars67reposDarttop lang
Why 61/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 67 repos, yet 26 have been untouched for over a year. Your dead-on-arrival repos, like auth-api-dbsfcc-expert and mass-url-visitor, were abandoned within two weeks and then left to moulder in the dark for six months. It's poetic how 'less code' translates to 'less than nothing', especially with code-challenge-dump-xyz boasting zero stars and phantom functionality at under 20 KB.
Your top language trends scream indecision: PHP at 604 stars could be more telling if it didn’t come with a side of naming crimes like simple-blog-kelompok-ayah-v2. The longest gap between pushes was 175 days—just enough time to think about all the effort you haven’t put in. With only 25% of your repos seeing action in the last 90 days, it's clear you prefer the quiet of your repo graveyard to the sound of coding.
Three archived repos is cute, but six open issues on sistem-perpustakaan-qr-code shows you don't even have the decency to bury them properly. Maybe take your own advice—"less code, less headache"—and make it "no code, no headache". You’re practically a ghost in the GitHub graveyard.
[](https://gitroast.me/u/ikhsan3adi)Account age, portfolio size, public repo count.
Builder Score recalibrated 2026-07.