🏦 Open source, transparency-orientated fiscal sponsorship platform for hackers & creatives.
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 9%
Response Time: 13h
First Timer Success: 11%
hackclub/hcb has a recorded first-timer success rate of 11.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in hackclub/hcb respond to incoming external pull requests in approximately 12.9 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 59.7 places hackclub/hcb in the A tier.
The external contributor pull request merge rate for hackclub/hcb is 9.4%, based on public PR activity from non-core contributors.
hackclub/hcb currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Ruby project in hackclub/hcb welcoming community pull requests and bug fixes.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/hackclub/hcb?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 22:00 UTC (22:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 21:00 to 01:00 UTC (21:00 - 01:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~8 hours (12% approval). Large PRs (>500 lines) take ~62 hours (15% approval). Keep your diff compact for rapid review.
At the moment, email notifications get sent to Intercom. It has latency bc we gotta wait for ops to assign the ticket to us. Let's reconfigure Blazer so emails go to hcb-engr@ by default
Describe your goals Several list pages (Transfers, Invoices, Payments, Reimbursements, Sub-organizations) share a filter bar. You pick a filter from a dropdown and it appears as a removable chip showing what's applied. Filter chips use .humanize to render the labels. This works most of the time, but there are certain cases where we want to intentionally make a word capitalized, for example: Note the chip is the only thing that's wrong here; the dropdown you picked it from renders "HCB transfer" correctly. The two disagreeing is a good clue about where the problem is. The right shape is a single shared way of resolving a filter value to its display label, used by both the chip and the dropdown, so they can't drift again. There's an older filter implementation elsewhere in the app that handles this with a hardcoded chain of string replacements. Please don't extend that pattern. Replacing it too would be a bonus. Repro: an org's Transfers page with at least one HCB transfer, filtered by
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to hackclub/hcb, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of hackclub/hcb acknowledge new external contributions in approximately 12 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 9.4% were successfully merged into the primary branch.
hackclub/hcb has a recorded first-timer success rate of 11.1%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~12 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 59.7 places hackclub/hcb in the Welcoming tier.
The external pull request merge rate is 9.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, hackclub/hcb currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for hackclub/hcb are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.