← Back to Hall of Fame
🔍 Fetching their open-source footprint (repos / languages / contributions)…
Score breakdown
Account maturity9.5 / 10
Original project quality4.5 / 18
Contribution quality20.1 / 27
Ecosystem / maintenance impact13.2 / 20
Community influence2.5 / 8
Activity authenticity14.0 / 17
🧬 Most similar developers
Closest profile, nearby score
🔥 Full roast
🔥 You dropped 72 PRs and 48 commits into PaddlePaddle's 24k-star repo, yet all your 23 original repos have a combined total of 1 star, you hoard 25 forks, and you follow 19 people while only 9 follow yo
Manfredss — 63.80/100 · NPC (Average · Unremarkable)
TL;DR: Heavy on templated API-compatibility patches for PaddlePaddle, light on original project value, and your home turf is a starless wasteland—solid ecosystem grunt work, zero standalone signal.
| Dimension | Score | Notes |
|---|---|---|
| Account maturity | 9.5/10 | Registered 5.61 years, active across 7 contribution years—you've been on GitHub longer than most of your original repos have had any stars. |
| Original project quality | 4.5/18 | 23 original repos, total combined stars = 1, top-starred original repo (Agent) quality score 0.3—your best original project is a LangChain agent template with fewer stars than a bug report, your "llama" repo is just redistributed Meta Llama 2 weights, and 22 of your 23 original repos sit at a lonely 0 stars. |
| Contribution quality | 20.1/27 | 80 merged PRs out of 123 total; 10 maintainer-closed unmerged, 14 author-closed external PRs, 1 author-closed own-repo PR. 67% of recent merged PRs follow the same [API Compatibility] template, and only 3 of 50 recent merged PRs touch docs/site/examples—you're not spamming, you're just on a very repetitive assembly line. |
| Ecosystem / maintenance impact | 13.2/20 | 72 PRs + 48 commits into ★23,998 PaddlePaddle/Paddle and ★282 PaddlePaddle/docs (all-time). Verified file samples show real code/test changes across core APIs, not just window dressing—your work actually lands in one of the biggest AI framework repos, even if it's all compatibility patch grunt work. |
| Community influence | 2.5/8 | 9 followers, 19 following—your follower count is lower than the number of repos you've forked, and you're following more people than follow you, a classic signal of someone fishing for clout instead of building something people care about. |
| Activity authenticity | 14/17 | 340 contributions last year, active as of today—no ghostwriter signs, you're actually putting in the hours, just all of it is directed at other people's projects and templated patches. |
| Red flags |
- Repetitive templated contribution pattern: 67% of your recent merged PRs use nearly identical [API Compatibility] titles and follow the same patch structure, suggesting you're working off a fixed task list rather than driving original, self-directed work.
- Barren original project portfolio: 22 of your 23 original repos have 0 stars, your top original repo is a LangChain agent template with no traction, and your "llama" repo is just redistributed Meta Llama 2 weights with no original engineering.
- Asymmetric social and curation metrics: You follow 19 accounts but only have 9 followers, and your 25 fork repos vastly outnumber your original project star count, signaling you're curating/consuming open source far more than you're building it. Score calibration No extra adjustment. The base score of 63.8 already accounts for your strong all-time ecosystem impact against your weak original project portfolio and repetitive contribution style; no additional bump or haircut was needed. Verdict Normal average contributor. You're a reliable grunt worker for large open-source projects, with no red flags for spam, fraud, or bad faith, but your profile lacks any standalone engineering signal to push you into a higher tier. Keep shipping those compatibility patches, but maybe try building something people actually want to star someday.