Pandosearch Bundle Laravel Package

Product Decisions This Supports

• Search vendor selection (build vs. buy): This bundle is a thin Symfony integration for the PandaSearch hosted search API. It is relevant only as a data point in the “buy” column for search-as-a-service — not as a recommended implementation.
• Legacy modernization / migration sequencing: Because it is archived (last release 2018-11-22), it is most useful as an input to decommissioning decisions: identifying search functionality that must be re-platformed, and scoping the effort of swapping search providers.
• Dependency risk assessment: With 0 stars and 0 dependents, it represents a single-vendor, single-consumer artifact. That is a concrete example for dependency-policy discussions (approved-vendor lists, abandonment-risk scoring) rather than a package to standardize on.
• Framework scope correction: Note the mismatch — this is a Symfony bundle, not a Laravel package. Any roadmap item assuming drop-in Laravel search support from this repo is based on a false premise and should be corrected before estimation.
• Not supported: Choosing search architecture, relevance tuning, indexing strategy, or any net-new feature work. There is no active maintenance, no community, and no security response path.

When to Consider This Package

Consider it only when all of the following hold:

• You are maintaining an existing Symfony application already integrated with PandaSearch.
• The bundle is already installed and working, and you need to read it to understand current behavior during a migration.
• You are scoping a replacement (e.g., Meilisearch, Typesense, Algolia, OpenSearch/Elasticsearch) and need to map the existing surface area.

Look elsewhere — and actively avoid adoption — when:

• You are on Laravel. This bundle targets Symfony’s bundle/kernel conventions and will not integrate without a rewrite. There is no Laravel equivalent in this repo.
• The work is net-new. Do not introduce an archived 2018 dependency into a new codebase; you inherit the abandonment risk with none of the community support.
• You need a maintained vendor client. PandaSearch’s own HTTP API / official SDK is the correct integration point; wrapping an unmaintained third-party bundle adds a layer with no owner.
• Security or compliance review applies. There is no release cadence, no CVE response, and effectively no downstream usage to surface regressions.
• You want community signal. 0 stars and 0 dependents means no ecosystem, no Stack Overflow corpus, and no peer review of the code.

How to Pitch It (Stakeholders)

For executives: This is an archived, single-consumer Symfony integration for a hosted search vendor. It is not a candidate for adoption and should not appear in any build-vs-buy recommendation. The strategic message is simple: our search capability must not depend on an unmaintained wrapper with no community and no security response path. If a team is currently relying on it, treat that as technical debt with a named migration owner and a target date, not as a platform.

For engineering leadership: The package is a thin adapter over an external search API — meaning the real dependency is the vendor, not the bundle. Replacement cost is therefore low and mostly mechanical: enumerate the call sites, reimplement against the vendor’s current API or a maintained alternative, and delete the bundle. Frame the work as a bounded refactor (days, not quarters), and use it as a forcing function to revisit whether hosted search-as-a-service still fits our relevance, latency, and cost requirements.

For the product team: No feature work should be planned against this dependency. If search quality, filtering, or relevance is on the roadmap, the prerequisite is a search platform decision made on current vendor evaluation — not on a 2018 Symfony bundle. Budget the migration explicitly rather than letting it hide inside unrelated tickets.

For any stakeholder assuming Laravel compatibility: Correct the record early. This is a Symfony bundle; there is no Laravel support here, and no maintained Laravel integration is implied by this repository.