Database

Meilisearch: supported versions and end-of-life dates today

Meilisearch 1.54 is supported; 1.53 reached end of life on Sep 21, 2026; the latest release is 1.54.3.

Last checked against endoflife.date and deps.dev.

Latest release
1.54.3
GitHub stars
59.6k
OpenSSF Scorecard
7.2 / 10

Supported versions

Meilisearch release lines and security support dates from endoflife.date
VersionSecurity supportLatestReleased
Meilisearch 1.54Supported: No end date announced1.54.3
Meilisearch 1.53Ended: Ended 1.53.3
Meilisearch 1.52Ended: Ended 1.52.4
Meilisearch 1.51Ended: Ended 1.51.0

Maintenance and supply chain

OpenSSF Scorecard 7.2 / 10 (scored )

The Scorecard rates the repository’s security practices, not known vulnerabilities. Recent activity: 30 commits and 5 issue updates found in the last 90 days.

Weakest checks

  • Over-privileged CI tokens (Token-Permissions 0/10)
  • Unsigned releases (Signed-Releases 0/10)
  • No OpenSSF best-practices badge (CII-Best-Practices 0/10)

Full ScorecardSource repository

Alternatives

  • Elasticsearch

    Distributed search and analytics engine

    Strengths

    • Powerful full-text search
    • Real-time indexing

    Trade-offs

    • High memory usage
    • Complex to tune and optimize
    Elasticsearch health today
  • Algolia

    Managed search and discovery API

    Strengths

    • Blazing fast search (<10ms)
    • Easy to implement

    Trade-offs

    • Vendor lock-in
    • Limited customization
  • Typesense

    Open-source alternative to Algolia

    Strengths

    • Fast search performance
    • Easy to set up

    Trade-offs

    • Smaller ecosystem
    • Fewer advanced features
  • OpenSearch

    Community-driven fork of Elasticsearch

    Strengths

    • Fully open-source (Apache 2.0 license)
    • Elasticsearch-compatible (easy migration)

    Trade-offs

    • Smaller ecosystem than Elasticsearch
    • Some divergence from Elasticsearch features
    OpenSearch health today

Check Meilisearch in your own stack

This page checks Meilisearch in general. Your repo pins specific versions: the free dependency check reads your manifests and lists what to fix first. Prism Agent runs the same live checks on your whole stack and turns them into a plan your coding agent can build.