meilisearch/meilisearch-php - Open Source PR Review Scorecard

PHP client for Meilisearch

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

External PR Merge Rate: 55%

Response Time: 7h

First Timer Success: 50%

Frequently Asked Questions

Is meilisearch/meilisearch-php welcoming to first-time open-source contributors?

meilisearch/meilisearch-php has a recorded first-timer success rate of 50.0%. 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 meilisearch/meilisearch-php respond to incoming external pull requests in approximately 6.5 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 meilisearch/meilisearch-php in the A tier.

What is the external contributor pull request merge rate for meilisearch/meilisearch-php?

The external contributor pull request merge rate for meilisearch/meilisearch-php is 54.5%, based on public PR activity from non-core contributors.

Are there Good First Issues available in meilisearch/meilisearch-php?

meilisearch/meilisearch-php currently has 11 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

meilisearch
meilisearch/meilisearch-phpAWelcoming754
GitHub
Back to Explorer
meilisearch

meilisearch/meilisearch-php

754
AWelcoming(59/100)PHP

PHP client for Meilisearch

Compare
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.7/10
Patience Score
8.2/10
Nitpick Rate
30%

Collaborative maintainer environment in meilisearch/meilisearch-php. Reviews community pull requests with focus on project quality.

Top PR Submission Do's

  • Ensure code complies with the project coding style
  • Keep PRs scoped to a single concern
  • Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • Do not submit PRs without linking an issue
  • Do not break existing tests without fixing them
  • Do not mix unrelated refactors in a single PR
Response Velocity
6 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
54.5%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
50.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
6 core
Highly collaborative maintainer core
Diagnostic Health HUD
54.5%
Merge Gauge
50.0%
1st-Timer
Community Vibe62/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

Context Meilisearch v1.53.0 adds indexSize and usedIndexSize to per-index stats. Objective Update the SDK so index stats responses include the new indexSize and usedIndexSize fields returned by Get stats of index and per index in Get stats of all indexes. indexSize: size of the index DB (bytes by default; honour sizeFormat when supported) usedIndexSize: size of the used pages of the index DB (bytes by default; honour sizeFormat when supported) Tasks Add indexSize and usedIndexSize to the index stats response shape Update test cases

📅 Opened Aug 11, 2026💬 0 comments
Quality: 90/100Contribute

Context Meilisearch v1.51.0 introduces filter conditions for Dynamic Search Rules (DSR). It also introduces a new lastUpdatedAt field in DSR responses. Objective Update the SDK to support: The new filter activation condition in the conditions object of a DSR. The filter condition contains a values key whose value is a JSON object mapping facet names to their expected filter values. The new lastUpdatedAt field returned by GET /dynamic-search-rules/{:ruleUid} and POST /dynamic-search-rules. Use these resources: Release notes Search Rules Overview — API reference Example of a DSR with a filter condition // PATCH /dynamic-search-rules/test-filter { "conditions": { "filter": { "values": { "color": "red", "category": "shirt" } } }, "actions": [ { "selector": { "indexUid": "products", "id": "123" }, "action": { "type": "pin", "position": 1 } } ] } Tasks Update the conditions parameter to accept the n

📅 Opened Jul 28, 2026💬 0 comments
Quality: 90/100Contribute

Context Meilisearch introduced document relations as an experimental feature. Objective Add support for the document relations settings as an experimental feature. Experimental features should require opt-in by the user. Read the how to guide for more information. Tasks Add methods to interact with Get foreignKeys, Update foreignKeys, and Reset foreignKeys API endpoints Update the global settings methods to accept and handle the foreignKeys setting Add test cases for all new methods Add code samples in .code-samples.meilisearch.yaml matching the Meilisearch documentation CURL examples: Under get_foreign_keys_setting_1: equivalent of this code sample Under update_foreign_keys_setting_1: equivalent of this code sample Under reset_foreign_keys_setting_1: equivalent of this code sample Resources Release notes: Meilisearch v1.39 introduced cross-index document hydration via a new foreignKeys index setting. This allows linking documents across indexes so that search results are

📅 Opened Jul 1, 2026💬 0 comments
Quality: 90/100Contribute

Context Meilisearch 1.48.0 introduces the render template route as an experimental feature. Objective Update the SDK to support the render template route as an experimental feature. Experimental features should require opt-in by the user. Tasks Add method to handle interacting with the render template API endpoint Add test cases for the new method Add a code sample in .code-samples.meilisearch.yaml, it should be the equivalent of the documentation's CURL example.

📅 Opened Jun 30, 2026💬 0 comments
Quality: 90/100Contribute

Context Meilisearch 1.47.0 adds full support for personalized search (experimental) to the search endpoint. NB: before 1.47.0, federated search requests did not support personalized search. Objective Update the SDK to support personalized search on the search endpoint. Update the corresponding SDK methods Search (POST) Search (GET) Both related API endpoints now accept a new personalize object parameter: { // other request parameters... "personalize": { "userContext": "The user prefers ..." } } Tasks Add/update methods to handle interacting with the search API endpoints Add/update test cases for the new/updated methods No code samples to update

📅 Opened Jun 16, 2026💬 0 comments
Quality: 80/100Contribute
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 meilisearch/meilisearch-php

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

Frequently Asked Questions - Contributing to meilisearch/meilisearch-php

01

Is meilisearch/meilisearch-php welcoming to first-time open-source contributors?

meilisearch/meilisearch-php has a recorded first-timer success rate of 50.0%. 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 ~6 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 meilisearch/meilisearch-php in the Welcoming tier.

04

What is the external contributor pull request merge rate for meilisearch/meilisearch-php?

The external pull request merge rate is 54.5%. 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 meilisearch/meilisearch-php?

Yes, meilisearch/meilisearch-php currently has 11 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 meilisearch/meilisearch-php 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.