Entreprise Search Bundle Laravel Package

Product Decisions This Supports

• Feature enablement: French company lookup — search by name or SIREN/SIRET, autocomplete on onboarding and KYC forms, invoice/account verification, supplier and customer record creation with authoritative legal identifiers.
• Build vs. buy: This is a thin wrapper, not a data platform. The real dependency is the upstream public company-search API (rate limits, uptime, data freshness). Adopting the wrapper buys days of integration work, not a data contract.
• Roadmap fit: Relevant only to France-facing flows. Useful as a low-cost spike to validate demand for company-enriched records before committing to a licensed provider (INSEE/INPI/Infogreffe) with SLAs.
• Reversibility: Small surface area means low switching cost if wrapped behind our own interface — a good property for a decision we may need to unwind.

Evidence caveat: v0.2.0's only published change is a CI/tests workflow badge. No changelog, feature list, or docs were included, so capability claims above are inferred from the package name and domain, not verified. Treat this assessment as provisional and confirm scope before any commitment.

When to Consider This Package

Consider it when:

• The product serves French businesses or consumers and needs SIREN/SIRET resolution inside a Laravel app.
• You want a working prototype in hours, not a procurement cycle.
• You can accept pre-1.0 churn — at v0.2.0, breaking changes should be assumed, so pin the version exactly.
• You can absorb upstream risk: cache aggressively, degrade gracefully, and never block a checkout or signup on a third-party lookup.

Look elsewhere when:

• You need multi-country coverage or non-French registries.
• The lookup is compliance-critical and needs a contractual SLA, audit trail, or licensed data provenance.
• Volume is high enough that public API rate limits become the binding constraint.
• Verify framework fit first: the "bundle" naming is Symfony convention, while the brief describes a Laravel package. Confirm a service provider, config publishing, and auto-discovery actually work before estimating.
• Governance matters: single-maintainer, zero-to-low adoption, and the test workflow only just landed. That is a positive signal, not a mature one.

How to Pitch It (Stakeholders)

For executives: A small open-source PHP component that lets our product look up French companies by name or registration number, so users stop typing legal details by hand. Cost is negligible and lock-in is low. The risk is maturity, not money — it is a v0.2.0 project from a single maintainer with no published documentation. Recommendation: greenlight a time-boxed two-week spike behind our own abstraction layer. Do not place it on a revenue-critical or compliance-critical path until we have either upstream SLAs or a fallback provider.

For engineering: Assume breaking changes. Pin the exact version, wrap it in our own CompanyLookup interface with a caching decorator, add contract tests against a recorded fixture set so upstream drift fails loudly, and instrument for upstream latency and error rates. Budget a day to confirm the package's Laravel integration primitives actually exist before committing to the estimate.