meilisearch/meilisearch-java - Open Source PR Review Scorecard

Java client for Meilisearch

C-Rank Grade: D (Risky) - 16/100

External PR Merge Rate: -

Response Time: 3d

First Timer Success: -

Frequently Asked Questions

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

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

What does the 15.8 C-Rank™ score (D 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 15.8 places meilisearch/meilisearch-java in the D tier.

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

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

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

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

meilisearch
meilisearch/meilisearch-javaD•Risky247
GitHub
Back to Explorer
meilisearch

meilisearch/meilisearch-java

247
InactiveD•Risky(16/100)Low Sample (<20 PRs)Java

Java client for Meilisearch

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
20%

Growing Java project in meilisearch/meilisearch-java welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • •Ensure code complies with Java style conventions
  • •Keep PRs scoped and well-documented

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
Response Velocity
2 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
0.0%
Selective PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
0.0%
No first-timer merges recorded in window

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
0.0%
Merge Gauge
0.0%
1st-Timer
Community Vibe0/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

Context Meilisearch v1.55.0 introduces dynamic search rule preview. Objective Update the SDK to support previewing a dynamic search rule by sending an inline rule on search and multi-search. This requires Meilisearch Enterprise Edition and the dynamicSearchRules experimental feature. POST /indexes/{indexUid}/search: { "q": "super hero", "inlineRule": { "uid": "user-likes-batman", "actions": { "scale": [ { "filter": "hero = batman AND release_time = fresh", "weight": 1.2 } ] } } } POST /multi-search with Meili-Include-Metadata: true header: { "queries": [ { "indexUid": "products", "q": "fashion", "filter": "color = blue AND category = shirt" }, { "indexUid": "products", "q": "fashion", "filter": "color = blue AND category = shirt", "inlineRule": { "uid": "special-sales", "conditions": { "query": { "words": "pants" },

📅 Opened Oct 13, 2026💬 1 comment
Quality: 75/100Contribute

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💬 2 comments
Quality: 40/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💬 3 comments
Quality: 40/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💬 1 comment
Quality: 30/100Contribute

Context [Meilisearch 1.44.0]https://github.com/meilisearch/meilisearch/releases/tag/v1.44.0) introduces human-formatted sizes and detailed DB sizes in stats. Objective Update the corresponding SDK methods: Get stats of index Get stats of all indexes Both related API endpoints now accept new query parameters: showInternalDatabaseSizes: boolean, optional, defaults to false. When present, the index stat objects in responses of the stat routes now contain an additional internalDatabaseSizes key, whose value is a dictionary of the internal database names and their current size in the index, like in the stats object of a batch. sizeFormat: human or raw: optional, defaults to raw. When present and set to human, then all database sizes in responses of the stat routes will be returned as a string containing an appropriate unit (MiB, GiB, etc). When missing or set to raw, then the current behavior of expressing the size in bytes as a number is retained. The keys in internalDatabaseSizes are

📅 Opened May 26, 2026💬 2 comments
Quality: 30/100Contribute
Looking for more Java beginner tasks?Explore Java 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-java

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

Frequently Asked Questions - Contributing to meilisearch/meilisearch-java

01

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

meilisearch/meilisearch-java has a recorded first-timer success rate of 0.0%. Repositories ranked Risky 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 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 15.8 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 15.8 places meilisearch/meilisearch-java in the Risky tier.

04

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

The external pull request merge rate is 0.0%. 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-java?

Yes, meilisearch/meilisearch-java currently has 8 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-java 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.