Api Platform Extensions Bundle Laravel Package

Product Decisions This Supports

• Feature scoping for search & retrieval APIs: This bundle directly informs whether UUID-based resource lookups and cross-entity "global search" belong in the next API iteration — the two capabilities product teams most often request once a read API ships.
• Build vs. buy vs. borrow: With 0 dependents and a last release of March 2023, this is best framed as borrow (reference implementation or vendored code) rather than buy. It's a small, MIT-licensed utility — the decision is really "spend ~1–2 engineer-days replicating this pattern" vs. "adopt and own an unmaintained dependency."
• Public identifier strategy: The UUID filter is the enabler for exposing non-sequential IDs externally (partner APIs, shareable links, customer-facing URLs) while keeping integer primary keys internal — a security and product-surface decision worth making explicitly.
• Omnisearch / admin dashboard roadmap: The global search filter maps to a common product ask (one search box across entities). This package gives a cheap way to prototype that experience before committing to a real search backend.
• Roadmap de-risking: Because adoption cost is low and reversibility is high, this is a safe spike candidate to validate demand for search features before investing in Elasticsearch/Meilisearch infrastructure.

When to Consider This Package

Consider it when:

• Your stack is Symfony + API Platform + Doctrine ORM. (Important: despite being catalogued as a "Laravel/PHP package," this is a Symfony bundle and will not drop into a Laravel application. API Platform is Symfony-first.)
• You need UUID filtering or simple multi-field/global search on Doctrine-backed resources and don't want to hand-write custom API Platform filters.
• You're comfortable forking and owning the code — 2 stars, 0 dependents, and no release since March 2023 means there is effectively no community, no security review, and no maintenance guarantee.
• Your API Platform version is old enough to be compatible; verify before committing.

Look elsewhere when:

• You're on Laravel — this package is not applicable; use Laravel-native filters or a search package instead.
• You need relevance ranking, fuzzy matching, faceting, typo tolerance, or scale beyond small tables — reach for Meilisearch, Typesense, or Elasticsearch rather than a Doctrine filter.
• Your organization requires actively maintained dependencies, published security advisories, or vendor support.
• You need it on a current API Platform release and can't absorb the cost of patching it forward yourself.

How to Pitch It (Stakeholders)

To executives: This is a small, free, MIT-licensed accelerator that can shorten delivery of search and filtering features by a day or two. It is not a strategic dependency — treat any adoption as a short-term convenience with a planned exit. Low cost, low risk, low lock-in; the main caveat is that the project is dormant, so we should budget a small amount of engineering ownership rather than assume it's "free."

To engineering: It's a thin Symfony bundle adding UUID, per-field search, and global search filters to API Platform over Doctrine ORM. Realistically we'd vendor or fork it — the code volume is small enough to read in an afternoon. Before adopting, verify API Platform compatibility and confirm we're okay owning patches. If the answer to either is no, replicate the filter logic in-house and move on; the pattern is more valuable than the package.