PHP-CMSIG/search - Open Source PR Review Scorecard

Search abstraction over different search engines written in PHP. Currently implemented Elasticsearch, Opensearch, Algolia, Meilisearch, Loupe, RediSearch, Solr, Typesense. Documentation: https://php-cmsig.github.io/search/

C-Rank Grade: A (Welcoming) - 59/100

External PR Merge Rate: 74%

Response Time: 2h

First Timer Success: 67%

Frequently Asked Questions

Is PHP-CMSIG/search welcoming to first-time open-source contributors?

PHP-CMSIG/search has a recorded first-timer success rate of 66.7%. Repositories ranked A 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 PHP-CMSIG/search respond to incoming external pull requests in approximately 2.4 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 58.9 C-Rank™ score (A 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 58.9 places PHP-CMSIG/search in the A tier.

What is the external contributor pull request merge rate for PHP-CMSIG/search?

The external contributor pull request merge rate for PHP-CMSIG/search is 73.8%, based on public PR activity from non-core contributors.

Are there Good First Issues available in PHP-CMSIG/search?

PHP-CMSIG/search does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

PHP-CMSIG
PHP-CMSIG/searchAWelcoming440
GitHub
Back to Explorer
PHP-CMSIG

PHP-CMSIG/search

440
AWelcoming(59/100)PHP

Search abstraction over different search engines written in PHP. Currently implemented Elasticsearch, Opensearch, Algolia, Meilisearch, Loupe, RediSearch, Solr, Typesense. Documentation: https://php-cmsig.github.io/search/

Compare
Jump to:
Response Velocity
2 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
73.8%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
3 core
Small core review team
Diagnostic Health HUD
73.8%
Merge Gauge
66.7%
1st-Timer
Community Vibe78/100

Embed C-Rank Badge

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

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

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for PHP-CMSIG/search.

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 PHP-CMSIG/search

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

Frequently Asked Questions - Contributing to PHP-CMSIG/search

01

Is PHP-CMSIG/search welcoming to first-time open-source contributors?

PHP-CMSIG/search has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming 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 ~2 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 58.9 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 58.9 places PHP-CMSIG/search in the Welcoming tier.

04

What is the external contributor pull request merge rate for PHP-CMSIG/search?

The external pull request merge rate is 73.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 PHP-CMSIG/search?

PHP-CMSIG/search does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for PHP-CMSIG/search 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.