Free and Open Source, Distributed, RESTful Search Engine
C-Rank Grade: S (Elite) - 70/100
External PR Merge Rate: 79%
Response Time: -
First Timer Success: 71%
elastic/elasticsearch has a recorded first-timer success rate of 71.4%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in elastic/elasticsearch respond to incoming external pull requests in approximately 0.0 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 69.8 places elastic/elasticsearch in the S tier.
The external contributor pull request merge rate for elastic/elasticsearch is 79.4%, based on public PR activity from non-core contributors.
elastic/elasticsearch currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in elastic/elasticsearch. Ensure PR scope matches issue requirements closely before requesting review.
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/elastic/elasticsearch?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (36% approval). Keep your diff compact for rapid review.
Currently, we are logging a lot (i.e., ~100k a day in ECH (logging-*:cluster-elasticsearch*)) caught exception while handling client http traffic, closing connection at WARN level. A lot of those seem to stem from client shenanigans (e.g., client closing the connection) that do not deserve WARN but maybe DEBUG level. This is issue is about figuring out the appropriate level (i.e., which ones should be ERRORs in case of a bug or which should be downgrade to DEBUG). After figuring that out, we could do something similar to getCloseConnectionExceptionLevel to choose the appropriate level.
Both SecurityMigrationExecutor and SystemIndexMigrationExecutor are run-to-completion one-shot migration tasks rather than continuously-running services. They do not "persist" in any meaningful sense, instead they have some external retry mechanism, so it seems that they would better fit as just regular transport actions instead. Refactoring those task to not be persistent tasks would also get us one step closer to removing the automaticReassignmentOnShutdown() persistent task executor flag (see #138565) and making this feature default everywhere. See: #145753 for more details
ILMHistoryStore uses BulkProcessor to retry indexing history up to 3 times if it hits a EsRejectedExecutionException because the cluster was too busy. From what I can tell, SnapshotHistoryStore just makes a single attempt, and logs an error and moves on if it hits EsRejectedExecutionException. I have seen this several times in production logs. We ought to have SnapshotHistoryStore use BulkProcessor to make a few attempts before giving up.
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 elastic/elasticsearch, 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 elastic/elasticsearch acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 79.4% were successfully merged into the primary branch.
elastic/elasticsearch has a recorded first-timer success rate of 71.4%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 69.8 places elastic/elasticsearch in the Elite tier.
The external pull request merge rate is 79.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, elastic/elasticsearch 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 elastic/elasticsearch 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.