WordPress/plugin-check - Open Source PR Review Scorecard

A repository for the new Plugin Check plugin from the WordPress Performance and Plugins Team.

C-Rank Grade: B (Solid) - 54/100

External PR Merge Rate: 56%

Response Time: 18h

First Timer Success: 69%

Frequently Asked Questions

Is WordPress/plugin-check welcoming to first-time open-source contributors?

WordPress/plugin-check has a recorded first-timer success rate of 69.2%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in WordPress/plugin-check respond to incoming external pull requests in approximately 18.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 54.4 C-Rank™ score (B Tier) represent?

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.4 places WordPress/plugin-check in the B tier.

What is the external contributor pull request merge rate for WordPress/plugin-check?

The external contributor pull request merge rate for WordPress/plugin-check is 55.8%, based on public PR activity from non-core contributors.

Are there Good First Issues available in WordPress/plugin-check?

WordPress/plugin-check currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

WordPress
WordPress/plugin-checkBSolid360
GitHub
Back to Explorer
WordPress

WordPress/plugin-check

360
BSolid(54/100)PHP

A repository for the new Plugin Check plugin from the WordPress Performance and Plugins Team.

Compare
Jump to:

AI Maintainer Review Guidelines

Review Persona

Constructive Code Reviewer

Warmth Score
7.4/10
Patience Score
7.8/10
Nitpick Rate
33%

Balanced & professional review environment in WordPress/plugin-check. Maintains strict focus on technical quality and test standards.

Top PR Submission Do's

  • Add unit tests with >80% coverage for modified code paths
  • Run repository linter and code formatters locally before pushing
  • Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • Do not submit unlinked PRs without referencing an existing issue
  • Do not mix refactoring and feature logic into a single commit
  • Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
18 hours
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
55.8%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
69.2%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
25 core
Highly collaborative maintainer core
Diagnostic Health HUD
55.8%
Merge Gauge
69.2%
1st-Timer
Community Vibe60/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for WordPress/plugin-check
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/WordPress/plugin-check)](https://getmerged.abhishekco.de/WordPress/plugin-check?utm_source=github&utm_medium=badge)

Active Good First Issues (1)

View on GitHub

This repository currently has 1 open good first issue tickets available for newcomers.

View all good first issues directly on GitHub

Looking for more PHP beginner tasks?Explore PHP GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for WordPress/plugin-check

When evaluating whether to contribute to WordPress/plugin-check, 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 WordPress/plugin-check acknowledge new external contributions in approximately 18 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 55.8% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to WordPress/plugin-check

01

Is WordPress/plugin-check welcoming to first-time open-source contributors?

WordPress/plugin-check has a recorded first-timer success rate of 69.2%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~18 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 54.4 C-Rank™ score represent?

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.4 places WordPress/plugin-check in the Solid tier.

04

What is the external contributor pull request merge rate for WordPress/plugin-check?

The external pull request merge rate is 55.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in WordPress/plugin-check?

Yes, WordPress/plugin-check currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for WordPress/plugin-check 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.