🏆 Notable contributions
Popular open-source repos they've shipped to (commits + PRs)
Score breakdown
🛠 Featured work
Their own popular and pinned repositories
《PHP核心技术与最佳实践》内知识要点及Demo
PHPPersonal blog with Alibaba serverless & hexo
CSSDemo of ICA in image separation written in MATLAB
MATLABOpen crawler is used to crawl open source related data from public site
TypeScriptAlarm for statsd backend with express, bearcat & leveldb
JavaScript🧬 Stack & domains
🧬 Most similar developers
Closest profile, nearby score
🔥 Full roast
🔥 80% of your 689 merged PRs are locked into X-lab2017/open-digger grinding label YAMLs, while your 25 original repos have only 29 total stars — your GitHub is a data-labeling gig for others, and your o
frank-zsy — 85.20/100 · ELITE (Elite · Top-tier dev)
TL;DR: High-volume, low-diversity contributor with solid all-time impact on high-star open source projects, but his own project portfolio is a ghost town and nearly all his PRs are funneled into a single repo’s repetitive data maintenance work — he’s a reliable gig worker for open source, not a standalone engineering leader.
| Dimension | Score | Notes |
|---|---|---|
| Account maturity | 10/10 | Registered 11.86 years ago with contributions spanning 13 calendar years, giving him plenty of time to build a more diverse contribution portfolio than he has now. |
| Original project quality | 7.1/18 | 25 original repos with a combined 29 stars, top starred original repo (frank-zsy/PHPCoreTechnologyAndBestPractise) has only 11 stars and a 0.45 usability score — his best original work is a PHP notes repo with fewer stars than a viral meme tweet, and his highest-quality original project (ICA_Demo, 0.85 score) only pulled 3 stars. |
| Contribution quality | 27/27 | 689 merged PRs out of 728 total, only 2 maintainer-closed unmerged PRs, 0 recent trivial PRs, recent external doc-like ratio 10% — his PR hit rate is squeaky clean, no spam or low-effort farming detected in the recent sample, even if a big chunk of his all-time output is repetitive label edits. |
| Ecosystem / maintenance impact | 19.6/20 | 395 PRs + 551 commits across 24 popular repos (including mem0ai/mem0, alibaba/arthas, alibaba/nacos, etc., max repo stars 59,885), with 330 contributions lacking file-level quality samples — his all-time footprint on high-star open source is legit, but we only have proof of quality for the open-digger slice, the rest is a black box. |
| Community influence | 6.5/8 | 191 followers, follows only 15 accounts — his follower count is pitifully low for someone with 11 years on GitHub and nearly 700 merged PRs, he’s not building a personal brand, just shipping code for other people’s projects. |
| Activity authenticity | 15/17 | 285 contributions last year, last activity 5 days ago, 13 active contribution years, 0 templated PR ratio, no PR flood suspect — he’s consistently active with no bot-like patterns, just churning out the same type of PRs for the same repo over and over. |
Red flags
- 80% of all merged PRs target X-lab2017/open-digger, meaning his contribution diversity across popular open source projects is basically zero — he’s a one-trick pony for a single repo’s label data maintenance work.
- The file-level quality sample only covers contributions to X-lab2017/open-digger; the quality of his 330+ contributions to other high-star popular repos (including mem0ai/mem0 and multiple Alibaba ecosystem projects) is completely unverifiable — he could be shipping core fixes or just one-line typo patches, we have no way to tell.
- A large portion of his recent PRs are bulk labeled data maintenance updates to open-digger, which are repetitive data entry tasks rather than core software engineering work — he’s not building features, he’s curating a taxonomy.
Score calibration No extra adjustment. The base score already accounts for his low-star original projects, extreme concentration of PRs to a single repo, and lack of verifiable quality for non-open-digger contributions. No additional bump or haircut was needed.
Verdict Normal, high-volume open source contributor whose impact is almost entirely tied to a single external repo’s data maintenance work, with no meaningful original project footprint to back up any claims of standalone engineering leadership. He’s a reliable worker for other people’s projects, but not a standalone engineering force.