Limit access to visitors who are logged in or allowed by IP addresses. Includes many options for handling blocked visitors.
C-Rank Grade: B (Solid) - 47/100
External PR Merge Rate: 100%
Response Time: -
First Timer Success: 100%
10up/restricted-site-access 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 10up/restricted-site-access 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 47.3 places 10up/restricted-site-access in the B tier.
The external contributor pull request merge rate for 10up/restricted-site-access is 100.0%, based on public PR activity from non-core contributors.
10up/restricted-site-access currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in 10up/restricted-site-access. Prompt code reviews with positive guidance for new contributors.
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/10up/restricted-site-access?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
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (45% approval). Keep your diff compact for rapid review.
Is your enhancement related to a problem? Please describe. Update PHP support to 8.2 through 8.5. using the PHP version support upgrade skill being developed in Fueled/.github#2 to analyze this repo and identify the changes needed. The update should: Raise the minimum supported PHP version to 8.2 Ensure the project supports and is tested through PHP 8.5 Update composer.json, plugin/package metadata, CI workflows, compatibility tooling, static analysis, readmes/docs, and related configuration as applicable Update dependencies where necessary for PHP 8.2–8.5 compatibility Remove or simplify compatibility code that only exists to support PHP versions below 8.2 where appropriate Address PHP 8.2–8.5 deprecations, compatibility issues, or test failures identified by the skill Update relevant documentation to reflect the new supported PHP range Avoid unnecessary refactoring solely to adopt newer PHP syntax. Any larger modernization opportunities identified by the skill can be documente
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 10up/restricted-site-access, 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 10up/restricted-site-access acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
10up/restricted-site-access 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 ~-. 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 47.3 places 10up/restricted-site-access in the Solid tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, 10up/restricted-site-access 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 10up/restricted-site-access 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.