Main repository for crowdsec scenarios/parsers
C-Rank Grade: B (Solid) - 54/100
External PR Merge Rate: 50%
Response Time: 21h
First Timer Success: 100%
crowdsecurity/hub has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in crowdsecurity/hub respond to incoming external pull requests in approximately 21.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 54.0 places crowdsecurity/hub in the B tier.
The external contributor pull request merge rate for crowdsecurity/hub is 50.0%, based on public PR activity from non-core contributors.
crowdsecurity/hub currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in crowdsecurity/hub.
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/crowdsecurity/hub?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 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~14 hours (62% approval). Large PRs (>500 lines) take ~102 hours (22% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Python.
ctfcli is a tool to manage Capture The Flag events and challenges
High level asynchronous concurrency and networking framework that works on top of either Trio or asyncio
PyAirbyte brings the power of Airbyte to every Python developer. Powers the Airbyte Cloud Replication MCP.
Describe the bug Using the latest seafile sync client (v9.0.18) on Debian 13 to sync a library triggers the alert crowdsecurity/http-crawl-non_statics very quickly. I haven't tried any other versions, though. To Reproduce download the latest seafile sync client run it log in sync a library Of course this needs a Seafile server and a CrowdSec Security Engine. In my case, Seafile is behind a traefik reverse proxy instead of caddy and the engine parses the access log of traefik. Expected behavior The alert crowdsecurity/http-crawl-non_statics is not being triggered. Additional context The alert shows the following context information. method: GET status: 200 target_uri: /seafhttp/repo/<library uuid>/block/<block hash> Workaround I've added a whitelist parser to catch these events. It's based on the Nextcloud whitelist parser. Perhaps you could create one for Seafile, too. name: "opiateblush/seafile-whitelist" description: "Whitelist events from Seafile" filter: "evt.Meta.service == 'h
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 crowdsecurity/hub, 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 crowdsecurity/hub acknowledge new external contributions in approximately 21 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 50.0% were successfully merged into the primary branch.
crowdsecurity/hub has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~21 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 54.0 places crowdsecurity/hub in the Solid tier.
The external pull request merge rate is 50.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, crowdsecurity/hub 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 crowdsecurity/hub 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.