Supercharge WordPress Content Workflows and Engagement with Artificial Intelligence.
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 76%
Response Time: 1d
First Timer Success: 100%
10up/classifai has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in 10up/classifai respond to incoming external pull requests in approximately 35.8 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 58.8 places 10up/classifai in the A tier.
The external contributor pull request merge rate for 10up/classifai is 75.7%, based on public PR activity from non-core contributors.
10up/classifai currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (66% critical review signals). Ensure PRs strictly follow guidelines before requesting review in 10up/classifai.
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/classifai?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 14:00 to 18:00 UTC (14:00 - 18: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 ~23 hours (95% approval). Large PRs (>500 lines) take ~172 hours (34% 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 PHP.
FS PBX: World’s Best Open-Source PBX
Stack question type for Moodle
Open runtime environments for serverless cloud computing ⚡️
Is your enhancement related to a problem? Please describe. Some integrations of the TTS feature have shown some UX improvements to avoid having to leave a page open for hours and split long articles as well as ensure bylines and footnotes are "read". Let's investigate pulling these sorts of extensions into ClassifAI core. Designs No response Describe alternatives you've considered No response Code of Conduct I agree to follow this project's Code of Conduct
Is your enhancement related to a problem? Please describe. In December 2024, version 3.2.0 introduced a refactored settings screen. The legacy settings experience was intentionally left available via a filter for backward compatibility, but it is no longer supported. All service providers and features added since 3.2.0 only exist in the new settings experience, making the legacy screen effectively dead code. We should formally deprecate and fully remove the legacy settings screen and its associated filter in a staged, explicit way. Designs Proposed approach: Deprecation notice release (major release) Show an admin notice when the legacy settings filter is in use Add a clear deprecation notice in the Upgrade Notice section of readme.txt Add a changelog entry explaining that the legacy settings screen is deprecated and scheduled for removal Filter removal release (major or minor release, depending on timing) Remove the filter that allows the legacy settings screen to be displaye
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/classifai, 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/classifai acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.7% were successfully merged into the primary branch.
10up/classifai has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 58.8 places 10up/classifai in the Welcoming tier.
The external pull request merge rate is 75.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, 10up/classifai currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for 10up/classifai 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.