aeyakovenko/percolator - Open Source PR Review Scorecard

C-Rank Grade: D (Risky) - 20/100

External PR Merge Rate: -

Response Time: 7d

First Timer Success: -

Frequently Asked Questions

Is aeyakovenko/percolator welcoming to first-time open-source contributors?

aeyakovenko/percolator has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in aeyakovenko/percolator respond to incoming external pull requests in approximately 175.7 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 20.3 C-Rank™ score (D Tier) represent?

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 20.3 places aeyakovenko/percolator in the D tier.

What is the external contributor pull request merge rate for aeyakovenko/percolator?

The external contributor pull request merge rate for aeyakovenko/percolator is 0.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in aeyakovenko/percolator?

aeyakovenko/percolator does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

aeyakovenko
aeyakovenko/percolatorDRisky558
GitHub
Back to Explorer
aeyakovenko

aeyakovenko/percolator

558
DRisky(20/100)Rust

Open-source repository analyzed with precision C-Rank telemetry.

Compare
Jump to:
Response Velocity
7 days+
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
0.0%
Selective PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
0.0%
No first-timer merges recorded in window

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
0.0%
Merge Gauge
0.0%
1st-Timer
Community Vibe0/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for aeyakovenko/percolator
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/aeyakovenko/percolator)](https://getmerged.abhishekco.de/aeyakovenko/percolator?utm_source=github&utm_medium=badge)

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for aeyakovenko/percolator.

View all good first issues directly on GitHub

Looking for more Rust beginner tasks?Explore Rust GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for aeyakovenko/percolator

When evaluating whether to contribute to aeyakovenko/percolator, 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 aeyakovenko/percolator acknowledge new external contributions in approximately 7 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to aeyakovenko/percolator

01

Is aeyakovenko/percolator welcoming to first-time open-source contributors?

aeyakovenko/percolator has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~7 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 20.3 C-Rank™ score represent?

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 20.3 places aeyakovenko/percolator in the Risky tier.

04

What is the external contributor pull request merge rate for aeyakovenko/percolator?

The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in aeyakovenko/percolator?

aeyakovenko/percolator does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for aeyakovenko/percolator 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.