High-performance web crawling engine with bindings for 11 languages
C-Rank Grade: B (Solid) - 51/100
External PR Merge Rate: 37%
Response Time: 7h
First Timer Success: 25%
xberg-io/crawlberg has a recorded first-timer success rate of 25.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in xberg-io/crawlberg respond to incoming external pull requests in approximately 7.1 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.7 places xberg-io/crawlberg in the B tier.
The external contributor pull request merge rate for xberg-io/crawlberg is 37.1%, based on public PR activity from non-core contributors.
xberg-io/crawlberg does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Balanced & professional review environment in xberg-io/crawlberg. Maintains strict focus on technical quality and test standards.
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/xberg-io/crawlberg?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 Monday - Wednesday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (48% approval). Large PRs (>500 lines) take ~28 hours (17% approval). Keep your diff compact for rapid review.
poly lint is green in this repo, but not because the code is under the size and complexity limits. 79 findings across 43 files are listed individually in alef.toml under the # --- quality-debt baseline --- block. Why it is a per-file list and not a rule switched off Listing each file keeps the metrics active on every file that is not listed, so new code is still checked and new violations still fail. The cost is that each existing offender has to be paid off individually — which is exactly what makes each one a self-contained task. What one unit of work looks like Pick a path from the list below. Reduce its findings — extract helpers from long functions, early-return to flatten nesting, group wide parameter lists into a struct, split an oversized file by responsibility. Delete that file's entry from the baseline in alef.toml. Run the crate's/package's tests and poly lint — both must be green. Ground rules Behaviour must not change. This is restructuring, not redesign. No arith
Drop-reason: rb-sys 0.9.127 fails to compile against Ruby 4.0.2 mingw headers on x86_64-pc-windows-gnu: /usr/local/rbenv/versions/4.0.2/include/ruby-4.0.0/ruby/defines.h:63:11: fatal error: 'sys/select.h' file not found Restoring win-x64 needs either an rb-sys release that patches the mingw includes or a downgrade to Ruby 3.x cross-build target. See RC.49 publish run https://github.com/kreuzberg-dev/kreuzcrawl/actions/runs/27100535515 for full log. The windows-x64 entry was removed from the ruby-gem matrix in .github/workflows/publish.yaml so the rest of the gem matrix can publish. Restoring it is the scope of this issue.
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 xberg-io/crawlberg, 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 xberg-io/crawlberg acknowledge new external contributions in approximately 7 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 37.1% were successfully merged into the primary branch.
xberg-io/crawlberg has a recorded first-timer success rate of 25.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~7 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.7 places xberg-io/crawlberg in the Solid tier.
The external pull request merge rate is 37.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
xberg-io/crawlberg does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for xberg-io/crawlberg 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.