Efficient embeddable adblocker library
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 55%
Response Time: 2d
First Timer Success: 33%
ghostery/adblocker has a recorded first-timer success rate of 33.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ghostery/adblocker respond to incoming external pull requests in approximately 55.7 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 59.5 places ghostery/adblocker in the A tier.
The external contributor pull request merge rate for ghostery/adblocker is 55.3%, based on public PR activity from non-core contributors.
ghostery/adblocker currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Efficient embeddable adblocker library
Active maintainer team in ghostery/adblocker welcoming community pull requests and bug fixes.
Discussions in ghostery/adblocker focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/ghostery/adblocker?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 04:00 UTC (04:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 01:00 to 05:00 UTC (01:00 - 05:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~36 hours (69% approval). Large PRs (>500 lines) take ~267 hours (25% approval). Keep your diff compact for rapid review.
The current querySelectorAll() behaviour of eval.ts is correct but written in very confusing way. This hugely delays the feature additions and bug fixes because the contributors cannot really estimate the true side-effects of the functions. They end up relying on the unit tests defining the behaviour and keep the internals black-boxed. This writing is to help other contributors understand how extended CSS works (especially about the internal evaluator) and bring the actual improvement regarding the structure. What are actual basic operations? The first step would be understanding the implementation requirements. matches(): test current element itself querySelectorAll(): select descendants under a scope traverse(): continue evaluating from an already-selected subject Those three behaviours are the very basic operations that we need to combine to make higher APIs available, and also the reason the whole structure is very confusing: in short - querySelectorAll and traverse have great ov
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 ghostery/adblocker, 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 ghostery/adblocker acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 55.3% were successfully merged into the primary branch.
ghostery/adblocker has a recorded first-timer success rate of 33.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 days+. 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 59.5 places ghostery/adblocker in the Welcoming tier.
The external pull request merge rate is 55.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ghostery/adblocker 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 ghostery/adblocker 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.