Framework Extra Bundle Laravel Package

Product Decisions This Supports

• Framework upgrade sequencing. This package is a fork of SensioFrameworkExtraBundle — a Symfony bundle, not a Laravel package — and upstream is deprecated. Adopting it forces a decision: hold the app on annotation-based controllers for one more release, or fund the migration to native PHP attributes now.
• Build vs. buy vs. migrate. The real choice isn't "use this vs. write our own"; it's "carry a forked dependency vs. move to what the framework already ships." Native #[Route], #[Template] (TwigBundle), #[IsGranted] (SecurityBundle), #[Cache], and #[MapEntity] now cover nearly everything this bundle provided.
• Controller conventions and code standards. @Template, @ParamConverter, @IsGranted, @Cache shape how controllers are written. This affects code review standards, onboarding, and how much framework-specific knowledge we screen for.
• Technical debt tracking. It gives us a concrete, dated line item: remove before the Symfony 7 upgrade, when the bundle will not be compatible.

When to Consider This Package

Consider only if:

• You run a legacy Symfony app (≤5.4) pinned to annotations and have no bandwidth this quarter for a migration.
• You specifically need ParamConverter entity resolution as a bridge until #[MapEntity].
• The fork is pinned to a commit and vendored, so you are not depending on upstream maintenance.

Look elsewhere if:

• You are on Symfony 6.2+ — use native attributes; this bundle adds nothing.
• It is a new project. There is no reason to start here.
• It is Laravel or any non-Symfony codebase — this is the wrong framework entirely.
• You need security patches, CVE response, or a support contract. A 0-star, 0-dependent, score-0 fork gives you none of that.

Risk flags to surface: zero stars and zero dependents mean it is effectively unvetted code. Treat it as untrusted: require a source review before install, and never let it sit on a critical path without an exit plan.

How to Pitch It (Stakeholders)

For executives: This is a community fork of an end-of-life Symfony bundle that lets controllers be configured with annotations rather than code. It is not a strategic investment — it is a bridge. The original is deprecated, and this fork has no community, no dependents, and no visible maintenance. My recommendation is that we do not adopt it as a new dependency. If a legacy service already uses it, budget a migration to native Symfony attributes within the next two release cycles. That migration is mechanical, low-risk, and removes an unmaintained supply-chain item from our footprint.

For engineering: Treat it as a stopgap only. Pin to a specific commit, audit the source, add a removal ticket tied to the Symfony 7 upgrade, and do not build new features that depend on its annotations.