Scraping repos…
Reading their public GitHub…
Colliery
@colliery-io · public profileROASTED
49/100
🔥 CERTIFIED MEDIOCRE
“Built one solid repo and still managed to average a star per dying project.”
CRank tierC-tier Work in Progress
Mint vaultArtifact · @colliery-io
Roast style
UNITED STATES
GITROAST.ME
Minted from @colliery-io’s public GitHub
10followers475stars21reposRusttop lang
Why 49/100
- Impact9.3/32
Stars on your live, original repos — discounted if it's all one viral hit.
- Community1.2/10
Developers who follow your work.
- Consistency13.4/14
How much of your live portfolio is actually active.
- Portfolio11.4/15
Substantive original repos and language range.
- Craft4.9/10
Descriptions, licenses, topics, live links — finished work.
- Recency5/5
Days since your last push to a live original repo.
The roast
Your GitHub is a star-party hosted by graphqlite, consuming 402 of your 475 total stars while the rest of your repos languish in shame. Three of your repos have fewer than 20 KB of code, and they’re so empty even the commitment to mediocrity disappears. Dual-backend-demo and rust-python-bridge both died within two weeks, leaving nothing but crickets and a silence that screams 'abandonment'.
With a whopping 295-day gap between pushes, your commits read like a ghost town, making it clear that your ‘work in progress’ isn’t even a warm-up. 80% of your repos were pushed in the last 90 days, proving you can sprint when under pressure, but the real question is: why do 19 repos only collectively hold 73 stars? One standout repo can’t mask a portfolio where mediocrity thrives, and that Builder Score of 49 reflects exactly that.
The flex
Your GitHub, as a badge.
[](https://gitroast.me/u/colliery-io)
