🏆 Notable contributions
Popular open-source repos they've shipped to (commits + PRs)
Score breakdown
🛠 Featured work
Their own popular and pinned repositories
🧬 Stack & domains
🧬 Most similar developers
Closest profile, nearby score
🔥 Full roast
🔥 Half your PRs are README/doc tweaks to your company's sealos repo, and most of the rest are templated 'deploy on sealos' drive-bys on hot projects. Out of 238 popular-repo PRs, only 28 touch core engi
fanux — 67.70/100 · NPC (Average · Unremarkable)
TL;DR: A GitHub profile that looks impressive on the surface (1.2k followers, 236 merged PRs) but is almost entirely docs/site polish and templated deploy guides for his employer's project, with core engineering work making up less than 12% of his high-star ecosystem contributions — classic resume packaging that needs human verification to rule out paid internal work logged as personal contribution.
| Dimension | Score | Notes |
|---|---|---|
| Account maturity | 10/10 | Registered 11.76 years, active across 13 contribution years, last activity 0 days ago — old account, but age doesn't equal engineering substance, as his PR history makes clear. |
| Original project quality | 14.3/18 | Total 961 stars across 37 original repos, with his top project lhttp pulling in 688 stars. The rest of his original repos are tiny, abandoned, or deprecated (kubeinit is marked dead, sealvm has 5 stars, most haven't seen a push in 5+ years) — his home turf is a ghost town except for one old project. |
| Contribution quality | 23.1/27 | 236 merged PRs out of 280 total, 17 maintainer-closed unmerged PRs, 20 self-closed external PRs. 90% of recent merged PRs are doc/site/README/deploy guide updates, with 14 trivial PRs in the recent sample — his contribution output is 90% window dressing, 10% actual work. |
| Ecosystem / maintenance impact | 8/20 | 238 PRs + 326 commits into 26 popular repos (all-time). Only 28 of those are core engineering PRs, 54 are doc-like, and the vast majority are sealos-related deploy docs — the mandatory impact cap is not just justified, it's overdue. |
| Community influence | 7.7/8 | 1,196 followers vs 32 following, a 37:1 ratio that looks like influence until you realize his own repos have almost no stars and his contribution substance is mostly docs — his follower count is a social filter, not a signal of engineering value. |
| Activity authenticity | 14.6/17 | 202 contributions last year, but 90% of recent PRs are doc/README updates, with a 17% templated PR ratio and 50% of his PRs targeting his employer's sealos repo — activity is real, but the substance is thinner than a README line. |
Red flags
- 90% of recent merged PRs are docs/site/README/deploy guide updates, with core engineering work making up less than 12% of his all-time high-star ecosystem contributions — his contribution portfolio is almost entirely window dressing for popular projects.
- 17% templated PR ratio, with multiple near-identical "add deploy on sealos" PRs submitted to different popular repos (NocoDB, Flowise, ChatAny, AlistGo docs) — this is templated contribution farming, not organic open-source work.
- 50% of all his PRs target his employer's
labring/sealosrepo, raising serious questions about the independence of his external contributions — there is no way to confirm if this is independent open-source work or paid internal work logged under his personal account. - The original scoring model failed to apply the mandatory impact quality cap, inflating his ecosystem impact score by nearly 10 points — the adjusted score correctly reflects the low engineering substance of his contributions.
Score calibration A mandatory 10-point deduction was applied because the base scoring model failed to enforce the required impact quality cap for doc-heavy ecosystem contributions. The original score of 77.7 overvalued his low-core-substance PR portfolio, so the cap was enforced to align the final score with actual engineering impact.
Verdict Needs human review. His GitHub profile reads like open-source resume theater: a high follower count, lots of PRs to popular projects, but almost all of it is docs/site polish and templated deploy guides for his employer's project, with very little core engineering work to back it up. A human needs to verify if his contributions are independent, substantive work or just resume padding and paid internal work logged under his personal account.