Templated Uri Bundle Laravel Package

Product Decisions This Supports

• Hypermedia API design (HATEOAS): If we ship HAL, JSON:API, Siren, or HAL-FORMS responses, links frequently need parameterization (/orders{?status,page,per_page}). RFC 6570 templates let the server publish one canonical link pattern and let clients expand it — this bundle is the Symfony-side plumbing for generating and routing those.
• API contract as a product surface: URI templates can become the single source of truth shared by OpenAPI links, reference docs, and generated SDKs. That's a docs/DevEx roadmap item, not just an engineering detail.
• Build vs. buy: Buy the concept, not necessarily the package. The bundle is thin glue around an existing PHP URI-template implementation plus Symfony router/DI wiring. Realistic build cost is small (days, not quarters) — so this is a "borrow the library, skip the bundle" decision unless we're already deep in Symfony bundle conventions.
• Framework fit is a gating decision: This is a Symfony bundle, not a Laravel package. If our stack is Laravel, it's out of scope as-is; the underlying RFC 6570 library is still usable, but the integration value drops to near zero.
• Use cases worth prototyping: filtered/paginated collection endpoints, multi-tenant path prefixes, deep links for mobile clients, and SDK/codegen inputs.

When to Consider This Package

Consider it when all of these hold:

• The service is Symfony and we want URI-template handling wired into the container/router rather than hand-rolled.
• We are actively emitting hypermedia links or OpenAPI links/callbacks that clients expand.
• We've verified the underlying template library's RFC 6570 level (1–4) covers our operators ({?}, {&}, {+}, {#}) — note 3.5.0 bumps the bundled router to hautelook/templated-uri-router 4.0, a major version jump, so pinning and a compatibility read of that library's 4.0 changelog are prerequisites.

Look elsewhere when:

• Stack is Laravel or framework-agnostic. Use rize/uri-template, guzzlehttp/uri-template, or similar directly — same capability, no bundle coupling.
• Maintenance risk matters. 3.5.0 is the first release since Jan 2023 and adds a new contributor, which is a mild positive signal — but the fundamentals are unchanged: roughly 1 star, 0 dependents, single-maintainer lineage (originally Hautelook, now under goetas), no evidence of security triage. One drive-by dependency bump does not constitute a maintenance guarantee.
• You need a supported, versioned dependency for a long-lived platform. A near-zero-adoption bundle is a fork-and-own liability, not a supply-chain asset — and a major transitive bump with no migration notes in the release is exactly the kind of churn a solo maintainer may not document.
• You only need client-side expansion — a JS/PHP template lib in the client or SDK does the job without server routing changes.

Treat the low opportunity score (38.11) as a signal: the capability is real, but this specific artifact is not where the leverage is. 3.5.0 is maintenance housekeeping, not a capability release.

How to Pitch It (Stakeholders)

To executives: This is a small, MIT-licensed component that would let our API publish parameterized link templates instead of hard-coded URLs — a modest DevEx/docs win. Cost is negligible, but so is strategic upside: near-zero adoption means we should fund it as a short spike, not a platform commitment. The latest release is a dependency bump, not a new capability, so nothing about the business case changes.

To engineering: Don't take the bundle as a dependency. Take RFC 6570. Validate the use case with the underlying URI-template library behind a thin internal interface, and only reach for the Symfony bundle if we specifically want its router integration. 3.5.0 bumps hautelook/templated-uri-router to 4.0 — if we do evaluate it, read that major-version changelog first, because the bundle release notes don't describe the impact. Pin the version and plan to own the fork; assume no upstream support.

Recommendation: Explore (timeboxed), do not adopt. Revisit only if hypermedia links become a committed roadmap item and we're on Symfony.