Distributed Peer-to-Peer Web Search Engine and Intranet Search Appliance
C-Rank Grade: B (Solid) - 50/100
External PR Merge Rate: 33%
Response Time: 1h
First Timer Success: -
yacy/yacy_search_server has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in yacy/yacy_search_server respond to incoming external pull requests in approximately 1.3 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 50.5 places yacy/yacy_search_server in the B tier.
The external contributor pull request merge rate for yacy/yacy_search_server is 33.3%, based on public PR activity from non-core contributors.
yacy/yacy_search_server currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in yacy/yacy_search_server 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/yacy/yacy_search_server?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 21:00 UTC (21:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (42% approval). Large PRs (>500 lines) take ~6 hours (15% approval). Keep your diff compact for rapid review.
Summary When the Recorded Actions list becomes very large (for example after crawling around 1 million domains), it becomes difficult to manage scheduled actions because all of the action buttons are only available at the bottom of the page. Problem On systems with a large number of recorded actions: The Recorded Actions table becomes several screens long. To execute or delete selected actions, the user must scroll all the way to the bottom. After making selections near the top of the table, it is inconvenient to repeatedly scroll to the bottom just to access: Execute Selected Actions Delete Selected Actions Delete old Actions Apply edited next execution dates This significantly slows administration when managing large crawl jobs. Steps to reproduce Create a large crawl (approximately 1 million domains is sufficient). Allow a large number of scheduled/recorded actions to accumulate. Open Automation. Select actions near the top of the list. Notice that all action buttons are only availa
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 yacy/yacy_search_server, 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 yacy/yacy_search_server acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 33.3% were successfully merged into the primary branch.
yacy/yacy_search_server has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 50.5 places yacy/yacy_search_server in the Solid tier.
The external pull request merge rate is 33.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, yacy/yacy_search_server 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 yacy/yacy_search_server 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.