Search Laravel Package

Product Decisions This Supports

• Platform-level build-vs-buy on enterprise search. This is not a standalone search product — it is the search subsystem of Ibexa DXP. Adopting it is only possible as part of an Ibexa DXP subscription, so the real decision it informs is "Ibexa DXP vs. a composable stack (CMS + Algolia/Elasticsearch/OpenSearch + custom UI)," not "should we use this library."
• Roadmap scoping for search UX features you would otherwise spec from scratch. The changelog evidences a fairly complete out-of-the-box feature set that maps directly to typical enterprise search backlog items:
  • Faceted filtering of global search results (IBX-3639)
  • Editor-facing sorting of result lists (IBX-6338)
  • Autocomplete / search suggestions, including total result counts in the suggestions endpoint (IBX-6413, IBX-7419)
  • Spell checking (IBX-6649)
  • Content-aware criteria building (e.g., date-based search criteria) and a PagerSearchDataMapper contract for pagination-aware result mapping
  • PM takeaway: if your roadmap contains those five items in the next 2–3 quarters, they are "already solved" line items under Ibexa — remove them from internal estimation and reallocate that capacity.
• Localization and content-governance decisions. Fixes touching language-selector placeholders, breadcrumb suppression in suggestions, and "Content Type" wording indicate the search layer is editor-facing and localized — relevant to decisions about multilingual site rollouts and editorial UX standards.
• Licensing and procurement risk gates. The dual license (Ibexa Business Use License or GPLv2) is a hard fork in the decision tree: GPLv2 copyleft is incompatible with closed-source distribution, so this package is only usable in proprietary contexts with a paid DXP subscription. This should trigger legal review before architecture sign-off, not after.
• Upgrade-window planning. Version lines track Ibexa DXP releases (4.6.x LTS and 5.0.x). PHP 8.3 is now the floor and Symfony 6→7.4 LTS migrations have already landed. This gives you a defensible platform-support horizon for a multi-year roadmap commitment.

When to Consider This Package

Consider it only when all of the following hold:

• You are already committed to (or actively shortlisting) Ibexa DXP / Ibexa Open Source as your content platform. This package has zero value outside that runtime.
• You need editor-facing, faceted, spell-checked, autocomplete-enabled search across structured content — not a general-purpose search index for arbitrary application data.
• Your distribution model permits the Ibexa BUL (i.e., you hold a valid DXP subscription), or your project is genuinely GPLv2-compatible.
• You are on, or can move to, PHP 8.3+ with Symfony 6/7 — the 5.0 line has dropped the BC class_alias layer, so 4.x→5.x is a real migration, not a patch bump.
• You value upstream maintenance continuity over feature velocity: consecutive releases (v5.0.4, .5, .8, .9; many 4.6.x) carry the note "No significant changes," which signals a stable, maintenance-mode component — good for stability, poor for anyone hoping for rapid capability growth.

Look elsewhere when:

• You are not on Ibexa. There are 4 GitHub stars and 0 dependents. There is no community, no independent integration ecosystem, no third-party tutorials, and no self-contained documentation — the README defers entirely to doc.ibexa.co. You will be entirely dependent on vendor support for troubleshooting.
• You need a search product with its own roadmap and API surface. Candidate alternatives by need: Algolia / Typesense / Meilisearch for managed relevance and typo tolerance; Elasticsearch/OpenSearch directly for full infrastructure control; Laravel Scout for framework-native indexing.
• You require permissive licensing. "NOASSERTION" on the license field is a red flag for automated compliance tooling; the actual terms are dual BUL/GPLv2, and the GPLv2 arm is copyleft. Do not let a scanner silently approve this.
• You need transparent, public change history — Atlassian and issues.ibexa.co ticket references are not publicly readable, so you cannot audit what a fix actually changed.
• You are evaluating a build-vs-buy decision at the component level. The answer here is neither build nor buy — it is "inherited." It comes with the platform or not at all.

How to Pitch It (Stakeholders)

To executives (one paragraph):

This is not a commercial product we can procure — it is an internal component of the Ibexa digital experience platform, which we would only obtain by licensing Ibexa DXP. The strategic question is therefore whether we standardize on Ibexa as our content platform. If we do, search comes bundled with faceting, sorting, autocomplete, and spell-check already implemented and maintained by the vendor, removing several quarters of custom search work from our roadmap. If we do not, this package has no path to adoption. Two caveats warrant a decision: the licensing is dual (commercial subscription or GPLv2 copyleft), which legal must clear for any closed-source distribution, and the component is explicitly maintenance-mode — releases are frequent but largely empty, so we should not expect search innovation from this layer alone.

To engineering:

• Treat it as a platform-owned dependency, not a library to evaluate. Version-pin to the Ibexa DXP release line (4.6 LTS or 5.0) and never to ibexa/search independently.
• Budget for the 4.x→5.x jump properly. PHP 8.3 minimum, Symfony 6 then 7.4 LTS, plus removal of class_alias BC shims — expect extension points and any local overrides to break.
• Extend through the published contracts, notably the PagerSearchDataMapper interface, rather than monkey-patching. That is the vendor's sanctioned seam for customizing paged result mapping.
• Own your own test coverage. There is no external consumer base (0 dependents) to surface regressions, and upstream defects have historically been subtle and behavioral — e.g., suggestions only matching whole words (IBX-7236), then partial-word search being removed (IBX-7512), and full-text criteria over-matching across all text fields (IBX-7361). Those are exactly the bugs that reach production and get blamed on engineering.

To procurement / legal:

License metadata reports "NOASSERTION," but the repository states a dual Ibexa Business Use License v2.4+ or GPLv2. Confirm in writing that our DXP subscription covers all environments (including non-production and any redistributed components), and confirm that no GPLv2-licensed portion is linked into anything we ship as proprietary. Do not let automated license scanning close this item on its own.