Scraping repos…
Reading their public GitHub…
1minds3t
@1minds3t · public profileROASTED
43/100
🔥 COMMITTED TO FAILURE
“One repo star shines bright while the rest gather dust.”
CRank tierC-tier Work in Progress
Mint vaultArtifact · @1minds3t
Roast style
GITROAST.ME
Minted from @1minds3t’s public GitHub
2Kfollowers126stars25reposPythontop lang
Why 43/100
- Impact6.5/32
Stars on your live, original repos — discounted if it's all one viral hit.
- Community5.7/10
Developers who follow your work.
- Consistency12.1/14
How much of your live portfolio is actually active.
- Portfolio8.4/15
Substantive original repos and language range.
- Craft4.2/10
Descriptions, licenses, topics, live links — finished work.
- Recency5/5
Days since your last push to a live original repo.
The roast
With only 126 stars across 25 repos, your output screams more "graveyard" than "builder." Three projects, lollama, omnipkg-runtime, and omnipkg-vscode, created and abandoned within two weeks, are a clear signal that you enjoy a quick fling with code but lack commitment. 46% of your original repos don’t even bother with descriptions—who needs clarity when you have confusion?
The push cadence reveals a desperate last-ditch effort: 23% of your repos received attention in the last 90 days, and the longest gap between pushes was 101 days. The only repo making any noise is omnipkg with 52 stars, while the rest echo the silence of your abandoned plans. A 43/100 Builder Score? Looks like your code runs faster than you do out of ideas.
The flex
Your GitHub, as a badge.
[](https://gitroast.me/u/1minds3t)
