Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 01:01 UTC

meilisearch / meilisearch-php

PHP client for Meilisearch

PHPMIT★ 757 stars⑂ 124 forkssince Dec 2019View on GitHub ↗

meilisearch/meilisearch-php holds a health index of 96 out of 100, placing it in the Exceptional band. It scores highest on Vitality (92/100) and lowest on AI Readiness (64/100). It was last updated today. 4 contributors account for most of its recent work.

96
overall / 100
Exceptional

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

96
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 83 is calibrated to 96 on the published index scale (record calibration 2026-08-02).

Ownership

MeilisearchOrganization
1,319 followers133 public repossince Sep 2018

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistmeilisearch/meilisearch-phpv2.0.0-beta.71,308,7227949 days agophpapiclientsearchinstantmeilisearch

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

92Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
22.8/36Commit cadence — 33/52 weeks with commits
18/18Commit volume — 154 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year154
human_commit_share0.95
days_since_last_push0
active_weeks_last_year33

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 77 releases published
36/36Release recency — latest release 29 days ago
27/27Release cadence — a release every ~37.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count77
latest_release_tagv1.17.0
releases_from_tagsno
days_since_latest_release29
mean_days_between_releases37.2
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

78Good · 17% of overall
How it's scored
46.7/60Stars — 757 stars
17.4/25Forks — 124 forks
5/15Watchers — 9 watchers
Inputs used
forks124
stars757
watchers9
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com, shields.io
has_pull_request_templateyes
How it's scored
80/80Monthly downloads — 1,308,722 downloads/month across packagist
14.3/20Registry dependents — 137 packages depend on it
Inputs used
packagesmeilisearch/meilisearch-php
dependents137
ecosystemspackagist
total_downloads19,334,491
monthly_downloads1,308,722
unverified_packages_excluded—

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

87Excellent · 23% of overall
How it's scored
43.2/54Bus factor — 4 contributor(s) cover half of all commits
18.5/22.5Commit distribution — top contributor authored 18% of commits
13.5/13.5Contributor breadth — 69 contributors
10/10OpenSSF Scorecard: Contributors — project has 39 contributing companies or organizations
Inputs used
bus_factor4
contributors_sampled69
top_contributor_share0.177
How it's scored
35.7/42Issue resolution — 85% of issues closed
26.4/30PR acceptance — 592/673 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs592
open_issues37
closed_issues209
prs_merged_7d1
prs_decided_7d1
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.85
closed_unmerged_prs81
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
22.4/25Owner reach — 1,319 followers of meilisearch
25/25Track record — 133 public repos, account ~7 yr old
Inputs used
followers1,319
owner_typeOrganization
is_verifiedno
owner_loginmeilisearch
public_repos133
account_age_days2,918

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 49 days ago
20/20Version history — 79 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesmeilisearch/meilisearch-php
ecosystemspackagist
any_deprecatedno
min_days_since_publish49

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows — 6 workflow(s)
24/24Tests present
16/16Linter config — .php-cs-fixer.dist.php
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 7 out of 7 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://meilisearch.com
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicsmeilisearch, sdk, client, php
has_wikiyes
homepagehttps://meilisearch.com
docs_sitehttps://meilisearch.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

72Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 7 out of 7 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 39 contributing companies or organizations
0/10Dangerous-Workflow — no data
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate7.2
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. Remaining weights renormalized.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

64Moderate · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, src/Contracts/AGENTS.md, src/Endpoints/AGENTS.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://meilisearch.com/llms.txt)
12.4/40Legible commit history — 22 of 95 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://meilisearch.com/llms.txt
legible_history_share0.232
agent_instruction_filesAGENTS.md, src/Contracts/AGENTS.md, src/Endpoints/AGENTS.md
agent_instruction_max_bytes352
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .php-cs-fixer.dist.php
0/11Static type checking
10/10Reproducible environment — Dockerfile
10/10Demonstrated agent practice — 13 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 5 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.13
toolchain_manifests—
dependency_bot_commit_share0.05
How it's scored
0/45Type-checkable code — PHP without a type-check config
55/55Manageable file sizes — 0/192 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes36,303
source_files_sampled192
oversized_source_files0

Key facts

757GitHub stars
69contributors
154commits, last 12 months
0days since last push
77releases
4bus factor
37open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 124 ⇿
0Stars
124Forks
74Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

025507510012512342020-042023-062026-08
Major 1Minor 34Patch 31

Each point covers 6 days.

OpenSSF Scorecard 7.2 / 10
7.2aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-09-10 01:00 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests7 out of 7 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 39 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
Packagistpsr/http-client^1.0composer.json
Packagistsymfony/polyfill-php81^1.33composer.json
All dependencies 13

Full resolved dependency set from the GitHub dependency graph: 2 direct and 11 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
Packagistpsr/http-client—direct
Packagistsymfony/polyfill-php81—direct
Packagistext-json—indirect
Packagisthttp-interop/http-factory-guzzle—indirect
Packagistphp—indirect
Packagistphp-cs-fixer/shim—indirect
Packagistphp-http/discovery—indirect
Packagistphpstan/phpstan—indirect
Packagistphpstan/phpstan-deprecation-rules—indirect
Packagistphpstan/phpstan-phpunit—indirect
Packagistphpstan/phpstan-strict-rules—indirect
Packagistphpunit/phpunit—indirect
Packagistsymfony/http-client—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — Packagist.