Framework Extra Bundle Laravel Package

Product Decisions This Supports

• Platform mismatch — first call to make: despite the framing, this is a Symfony bundle (QafooLabsNoFrameworkBundle), not a Laravel package. It has zero bearing on a Laravel roadmap and should be removed from any Laravel build-vs-buy comparison.
• Legacy modernization strategy: the bundle exists to help run Symfony incrementally inside a legacy PHP application ("no framework" bridging). Its value to us is as a reference architecture for strangler-fig / incremental migration, not as a dependency.
• Build vs buy for a compatibility layer: answers "can we adopt an existing bridge instead of writing our own?" Verdict: no — copy the pattern, don't take the dependency.
• Ecosystem signal for roadmap scoring: 123 stars, 0 dependents, archived, opportunity score ~1.87. This is the profile of an abandoned artifact. It informs how we score similar candidates (maintenance status, dependent count, last release) more than it informs any feature.
• Due diligence input: useful evidence that bridge layers are typically small and short-lived; the right long-term answer is usually to finish the migration and delete the bridge, not to vendor one.

When to Consider This Package

Consider it only as reading material, and only if all of the following are true:

• You maintain a legacy Symfony 2/3-era application and are planning an incremental migration.
• You want concrete prior art for request/response and session bridging between a legacy front controller and Symfony's kernel.
• You have confirmed you are not shipping it — no composer require in production.

Look elsewhere if any of these apply:

• You're on Laravel. Not applicable; use Laravel's own service providers, middleware, and bootstrap/app.php for incremental adoption.
• You're on Symfony 5/6/7. Native kernel events, HttpKernel listeners, and PSR-15 middleware cover this ground with active support.
• You need a supported dependency. Archived + zero dependents means no security patches, no version bumps, no maintainer response.
• You need anything with a license/security review. Don't spend review cycles on a repo you won't ship.

How to Pitch It (Stakeholders)

To executives: We evaluated qafoolabs/framework-extra-bundle and recommend no action. It is an archived Symfony add-on with negligible adoption (0 dependents) and no maintenance path. There is no cost, risk, or schedule impact because we are not adopting it; the only output is a short write-up of the incremental-migration pattern it demonstrated.

To engineering: Treat this as a 30-minute read, not a dependency. It is a compact example of bridging a legacy PHP entry point into a Symfony kernel — useful context if we ever build a strangler-pattern adapter. If we do build one, we build it in-house against our current framework version rather than importing an abandoned bundle.

Positioning: Research input, not a commitment. The recommendation is to close the evaluation, note the pattern in our migration playbook, and re-open only if a legacy Symfony bridge becomes an active roadmap item — at which point we'd scope a small in-house adapter instead.