Ezplatform Search Extra Laravel Package

Product Decisions This Supports

• Build vs. buy (tactical, not strategic): this is a thin, free utility layer on top of eZ Platform's Search API / Solr bundle. It informs the "do we write our own sort clauses and search criteria or take a dependency" decision — the answer is almost always "take the 200 lines and fork them" rather than "adopt and track upstream."
• Platform roadmap / migration sequencing: the last release (March 2021) predates the eZ Platform → Ibexa DXP rebrand and the 4.x line. Use its staleness as a data point in the "stay on eZ Platform 2.x/3.x vs. migrate to Ibexa 4" decision. If search customization is still on the roadmap, budget for the migration, not for extending this package.
• Feature scoping for search requirements: useful when a spec says "sort by random," "sort by a custom field," or "filter by attribute not covered by the core criteria." It tells you whether a request is a half-day job or a sprint — usually half a day.
• Dependency risk register entry: 13 stars, single-vendor (Netgen, an agency), GPL-2.0, ~4 years without a release. That combination belongs on the risk register next to any decision to depend on it.
• Licensing gate: GPL-2.0 is copyleft. This is a hard "no" for closed-source distribution and a "review with legal" for SaaS where the code is conveyed. It shapes whether this can be a product dependency at all, independent of technical merit.
• Not a Laravel package: the brief frames this as a Laravel/PHP package; it is not. It targets eZ Platform's Symfony-based stack. Any evaluation should be routed to the legacy eZ/Ibexa team, not the Laravel team — otherwise you're scoring it against the wrong baseline.

When to Consider This Package

Consider it when:

• You already run eZ Platform 2.x/3.x (or an early Ibexa release) with the Solr/legacy search engine and need extra sort clauses or criteria the core doesn't ship.
• The requirement is narrow and well-understood (custom ordering, attribute-based filtering) and the alternative is writing that plumbing in-house.
• Your codebase is internal, GPL-compatible, or otherwise unencumbered by the copyleft terms.
• You can afford to vendor or fork it — assume you will own the code, not Netgen. Budget an engineer-day to read it and a small allowance per year to patch it.
• You're on a short timeline and a dependency beats a custom implementation by more than the cost of carrying it.

Look elsewhere when:

• The project is Laravel or any non-eZ PHP stack — there is no integration path here. Look at Laravel Scout plus Meilisearch/Typesense/Algolia, or direct Elasticsearch/OpenSearch clients.
• You are on Ibexa 4.x or planning to be — verify compatibility first; assume it does not carry forward without a fork.
• Your product is closed-source or the license terms are unclear — GPL-2.0 likely disqualifies it outright.
• You need faceted search UX, relevance tuning, or analytics — this is plumbing, not a search product. Buy a search service.
• You need a supported, patched dependency with an SLA — last release 2021 means no upstream security response.
• Your requirements are broad enough that you'd end up forking heavily; at that point the fork is the build, so price it as such.

How to Pitch It (Stakeholders)

To executives: This is a small, free, community-maintained add-on for our legacy eZ Platform search layer. It saves a few days of engineering on narrow search customization and costs nothing to license — but it is GPL-2.0, which constrains how we can ship it, and it hasn't been updated since 2021, so we'd be adopting code we'd have to maintain ourselves. It is not a strategic bet and not a reason to change our platform roadmap; treat it as a tactical gap-filler with a named owner and a known exit (fork into our own tree). The real decision it surfaces is the eZ → Ibexa migration timeline: if search work is still ahead of us, that migration is the project, not this package.

To engineering: A thin utility library that adds extra search criteria and sort clauses on top of eZ Platform's Search API. Low integration cost, low ongoing cost if we vendor or fork it. We are the maintainers from day one — no upstream patches since 2021, 13 stars, single-vendor origin. Check GPL-2.0 against distribution model before it lands in the product, and confirm it isn't being evaluated as a Laravel package, because it isn't one. Recommendation: spend the half-day reading the source; if it's under ~500 lines, copy the relevant parts into our own search layer and drop the dependency entirely.