Admin Search Bundle Laravel Package

Product Decisions This Supports

• Build vs. buy for admin search: This bundle is a reference implementation of "Elasticsearch-backed search inside an admin panel." It answers the question "has someone already wired ES into a Sonata admin UI?" — the answer is yes, but the artifact is archived. Net: it supports the decision framing, not the decision to adopt.
• Roadmap input for search/discovery features: Use it as a competitive/technical baseline when scoping "advanced search" (facets, relevance ranking, cross-entity search) for an internal admin tool. It shows the minimum integration surface: an indexer, a query builder, and an admin UI hook.
• Ecosystem-fit check: Flag for stakeholders that this is a Symfony/Sonata bundle, not a Laravel package. If our stack is Laravel, this is a pattern reference only — there is no drop-in path, and the "0 dependents" signal confirms nobody is maintaining the bridge.
• Vendor/maintenance risk register: A 2021 archive date and zero dependents is a clean case study for "abandoned dependency" policy — useful when justifying internal rules like "no archived dependencies in production" or "prefer first-party integrations."
• Opportunity signal (score 6.55): The high opportunity score reflects an unmet need (Elasticsearch-native admin search) rather than a good artifact. That's a cue to evaluate whether building a thin internal ES-admin layer is worth a sprint — likely cheaper than resurrecting an abandoned Symfony bundle for a non-Symfony stack.
• Sunset/migration planning: If any legacy Sonata admin still relies on this, it feeds a deprecation plan — replace with native Sonata search or a maintained ES client.

When to Consider This Package

Consider it only as a read-only reference when:

• You maintain a legacy Symfony/Sonata admin and need to understand a prior ES integration pattern before replacing it.
• You are writing an architecture decision record on admin search and want a concrete "what a bundle-level integration looks like" example.
• You are doing dependency archaeology — auditing whether an old service still transitively depends on it.

Look elsewhere (do not adopt) when:

• Any new feature work is involved. Archived since 2021, 19 stars, 0 dependents, no security patching — it fails every basic supply-chain gate.
• Your stack is Laravel. There is no adapter path; you'd be porting, not integrating. Use Laravel Scout + a maintained Elasticsearch driver instead.
• You need Elasticsearch 8.x / OpenSearch compatibility. A 2021 bundle predates current ES client major versions; expect breaking API drift.
• Compliance or SLA requirements exist. MIT license is fine, but "abandoned" means no CVE response, no support contract, no roadmap.
• You want a buy decision. There is no vendor here to buy from — this is a dead OSS artifact.

How to Pitch It (Stakeholders)

For executives (one paragraph): We evaluated sonata-project/admin-search-bundle, an open-source add-on that connects Elasticsearch to the Sonata admin interface. It is archived and unmaintained (last release January 2021, 19 GitHub stars, zero downstream dependents) and it targets the Symfony/Sonata ecosystem, not Laravel, so it does not fit our stack. My recommendation is not to adopt it in production. Its value to us is as a design reference and as a data point: there is real, unmet demand for Elasticsearch-native admin search, which is why it scores high on opportunity despite being dead. The decision it drives is build vs. buy vs. defer on admin search — and on that question, a thin in-house integration (or a maintained library in our own ecosystem) is the lower-risk path.

For engineering (the ask): Treat this as a spike input, not a dependency. One engineer, half a day: skim the indexer and query-builder to extract the integration pattern, then close the ticket. Do not add it to composer.json. If we proceed with admin search, we scope it against Laravel Scout + an actively maintained Elasticsearch client, with an explicit note in the ADR that the Sonata bundle was reviewed and rejected on maintenance and ecosystem grounds.

Decision requested: Approve "no-go on adoption; reference-only" and fund a 1–2 sprint discovery for an in-house/Laravel-native admin search layer.