yoanbernabeu/recherche-entreprises-bundle
Symfony bundle for searching French companies through the official Recherche d'entreprises API. Query by name, SIREN, SIRET, or address and get structured results with legal form, activity, and location details, all wrapped in a simple, injectable PHP service.
dirigeants unlocks beneficial-owner-style screens, signatory verification, and "who runs this company" UI — a common requirement in B2B onboarding, invoicing, and fraud checks. This is the first release where the package plausibly covers a KYB flow end-to-end, not just company identity.isAssociation fix signals that downstream logic (association vs. commercial entity handling) was previously wrong. If any roadmap item branches on legal status (pricing, tax treatment, contract templates), this release reduces the risk of shipping on bad data.Adopt when:
Look elsewhere when:
0.1.x community package with no support commitment; the underlying API is a public service with its own rate limits and availability characteristics.isAssociation fix in a patch release is itself evidence of evolving contracts.Watch items before adopting: the release history shows only two contributors and three PRs total, so bus factor is 1–2 people. Mitigate with an abstraction layer over the client so the dependency is swappable.
To executives: v0.1.1 of this open-source PHP component lets us look up French companies and — new in this release — their directors, using free government data instead of a paid vendor. It's a low-cost way to prototype B2B onboarding and compliance checks and validate demand before we sign a contract. Treat it as a cheap experiment, not infrastructure: no support, no SLA, very early stage, and a small contributor base.
To engineering: It's a thin Symfony bundle over the public Recherche d'entreprises API. This release adds dirigeants, corrects a wrong isAssociation value, and — importantly — adds CI, which is the first real quality signal. Still 0.1.x, so expect breaking changes; wrap it behind our own interface so we can swap to a commercial KYB provider (or a direct HTTP client if we're on Laravel) without touching product code. Recommend a short spike to confirm field coverage and API rate limits before we put it in a customer-facing path.
Recommendation: Re-evaluate, don't commit. Reopen the build-vs-buy decision after we've run a 1–2 week spike on real French customer data and stress-tested the underlying API's limits.
How can I help you explore Laravel packages today?