Two-Factor Authentication for WordPress.
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 26%
Response Time: -
First Timer Success: 14%
WordPress/two-factor has a recorded first-timer success rate of 14.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in WordPress/two-factor 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 56.9 places WordPress/two-factor in the A tier.
The external contributor pull request merge rate for WordPress/two-factor is 25.6%, based on public PR activity from non-core contributors.
WordPress/two-factor currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in WordPress/two-factor. 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/WordPress/two-factor?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 21:00 UTC (21:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (32% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
WordPress 7.1 has already hit the RC stage, and is final release is due out today, so it would be great to get some testing on the latest Two Factor version on WP 7.1 so we can bump the tested-up-to value to 7.1 and push that across to WPORG SVN so things report as current on the plugin page there.
Is your enhancement related to a problem? Please describe. Currently, Two-Factor configuration exists only as a section within the WordPress “Edit Profile” screen. There are plans to make this settings screen portable for other plugins (e.g., WooCommerce) via #335. When Enforce 2FA becomes available through a settings option (see #255) or via a filter, users who have not yet configured Two-Factor will effectively be pushed to the default WordPress profile edit screen. This is suboptimal for several reasons: The profile screen contains many unrelated fields and options (name, email, bio, etc.). There is no clear indication that the user is there specifically because 2FA enrollment is required. The experience is not structured or guided. It creates friction and confusion during login. This can result in: Users believing they are stuck on the profile edit page without understanding why. Users overlooking the 2FA section entirely. Increased support requests. A forced security policy
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 WordPress/two-factor, 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/two-factor acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 25.6% were successfully merged into the primary branch.
WordPress/two-factor has a recorded first-timer success rate of 14.3%. Repositories ranked Welcoming 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 56.9 places WordPress/two-factor in the Welcoming tier.
The external pull request merge rate is 25.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, WordPress/two-factor 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 WordPress/two-factor 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.