Companies House Bundle Laravel Package

Product Decisions This Supports

• Build vs. buy for UK company data: Whether to integrate Companies House directly, wrap it in-house, or buy a KYB/verification vendor. This bundle is a data point on the "wrap it ourselves" option — and a cautionary one.
• Onboarding roadmap: Any flow requiring UK entity lookup (company search, registered office, officers, filing history, charges) — B2B signup, KYB gating, credit/risk checks, or counterparty verification in a marketplace.
• Feature scoping: Defines the minimum viable API surface (search, profile, officers, filings) so you can size the in-house alternative rather than treating the vendor call as a black box.
• Framework strategy: The package is a Symfony bundle, not a Laravel package. If the stack is Laravel, this is a signal to standardize on framework-native integration patterns (HTTP client + typed DTOs) rather than importing bundles that drag in Symfony kernel assumptions.
• Dependency policy: 2 stars, 0 dependents, low score — a concrete case for a "no single-maintainer packages on the critical path" rule, and for treating small community wrappers as reference implementations rather than dependencies.
• Abstraction decision: Reinforces putting Companies House behind an internal CompanyRegistry interface so the provider (direct API, OpenCorporates, a KYB vendor) is swappable without touching product code.

When to Consider This Package

Consider it only when all of the following hold:

• The codebase is Symfony (this bundle wires into the Symfony service container; it is not usable as-is in Laravel).
• You need a throwaway prototype or internal back-office tool, not a customer-facing or compliance-critical path.
• You want a fast read of the Companies House REST API surface — endpoints, request shapes, auth handling — before writing your own client.
• You accept the maintenance risk of an unmaintained, near-zero-adoption dependency and are prepared to vendor/fork it.

Look elsewhere when:

• You're on Laravel. Use a Laravel-native package or, better, a plain HTTP client (Guzzle/Saloon) with your own DTOs — a Symfony bundle adds container and config coupling for no gain.
• It's production KYB or compliance work. You need retries, rate-limit handling (Companies House enforces strict limits), caching, OAuth2/API-key rotation, structured error handling, audit logging, and test coverage. None of that is guaranteed here.
• You need a maintained dependency. 2 stars and 0 dependents means no community backstop, no security review, no upgrade path. Budget the maintenance yourself.
• You need more than read access (filing submission, streaming/filing-event feeds) — this bundle targets the REST lookup API.

How to Pitch It (Stakeholders)

For executives: UK company data is a legitimate product capability — it shortens B2B onboarding and de-risks who we transact with. But this specific package is a two-star, zero-dependent Symfony bundle, and our stack is Laravel. Recommendation: do not adopt it as a dependency. Treat it as a free spec for the Companies House API, and fund a small in-house integration instead — roughly a one-to-two-day engineering spike plus ongoing ownership, with no third-party maintenance risk on a compliance-adjacent path.

For engineering: It's a thin Symfony wrapper over the Companies House REST API. Useful as a reference for endpoint coverage and request shapes; not a foundation. Build a CompanyRegistry interface with a Companies House adapter using the HTTP client, typed response objects, caching, and retry/backoff. Keep the provider swappable so a KYB vendor can slot in later without product changes.

The ask: Approve a short spike to validate the API surface and rate limits, and adopt a standing rule that single-maintainer, low-adoption packages don't go on critical paths.