ghfind
← Back to Hall of Fame

🏆 Notable contributions

Popular open-source repos they've shipped to (commits + PRs)

Score breakdown

Account maturity7.0 / 10
Original project quality8.7 / 18
Contribution quality21.5 / 27
Ecosystem / maintenance impact8.0 / 20
Community influence5.6 / 8
Activity authenticity14.2 / 17

🛠 Featured work

Their own popular and pinned repositories

🧬 Stack & domains

Top languages
Rust75%
Shell25%
Domains
cloudflareone-clickwarpwireguard

🧬 Most similar developers

Closest profile, nearby score

🔥 Full roast

🔥 3 years on GitHub with 59 PRs, over half are doc/script tweaks for big projects like XTLS, your highest-starred home repo is a 124-star one-click registration tool, your ecosystem impact was capped an

chise0713 — 60.00/100 · NPC (Average · Unremarkable)

TL;DR: A doc-and-script tweaker who pads their GitHub profile with contributions to popular open-source projects while their own original repos barely crack 100 stars, with a capped ecosystem impact that exposes the water weight in their open-source résumé.

DimensionScoreNotes
Account maturity7/10Registered 3.43 years, active across 4 contribution years with no recent gaps — you at least show up to the party, even if most of your gifts are other people's leftover wrapping paper.
Original project quality8.7/1821 original repos with 231 total stars, top home repo (warp-reg.sh) has 124 stars and a mediocre 0.49 quality score — your best original work is a one-click Cloudflare WARP registration script, and the rest of your repos are mostly unstarred Rust toys.
Contribution quality21.5/2759 merged PRs out of 71 total, 4 maintainer-closed unmerged (6% rejection rate), 5 self-closed external PRs, 15 trivial PRs in the recent 50 merged sample — you don't get bounced much, but over half your recent merged work is docs/site/examples/CI tweaks for big-name repos.
Ecosystem / maintenance impact8/2055 all-time PRs + 75 commits into high-star popular repos (10 PRs/11 commits to XTLS/Xray-core, 4 PRs/5 commits to KernelSU), but impact was capped: 17 of 22 verified samples are doc-like/CI tweaks, and 23 all-time contributions lack file-level verification — you're contributing to big projects, but not moving the needle on their core functionality.
Community influence5.6/853 followers, following 13 — a modest 4:1 ratio that barely outpaces random account noise, with no community traction beyond the PRs you submit to other people's repos.
Activity authenticity14.2/17413 contributions last year across 3 activity types — you're consistently active, but the volume is almost entirely small doc/script tweaks and external PRs, with no meaningful output on your own original projects.

Red flags

  • Ecosystem impact was capped due to a docs/site/examples-heavy contribution profile, with verified samples showing more doc-like (17) than core (15) PRs to popular repos.
  • 23 all-time popular-repo contributions lack file-level verification samples, making it impossible to confirm core engineering impact for over a quarter of your popular-repo work.
  • Your highest-starred original repo (warp-reg.sh) is a low-quality utility script (quality score 0.49) with only 124 stars, the best of your 21 original projects.
  • 53% of your recent external merged PRs are doc-like, with 15 trivial PRs (dependabot updates, README tweaks, CI fixes) in the recent 50 merged sample, indicating a focus on low-effort contributions to big projects for profile padding.

Score calibration No extra adjustment was applied; the base score was reduced by 5 points to comply with the 60-point cap for ecosystem impact that is docs/site/examples-heavy and lacks sufficient core engineering verification. The base score already accounted for your contribution volume, account maturity, and original project traction.

Verdict A perfectly average open-source repo tourist who uses low-effort contributions to popular projects to pad their GitHub résumé, with no meaningful original project traction or core engineering impact to back up the high activity volume. Your profile looks busy, but the substance is thinner than the README for your best-starred repo.