Loopback Api Bundle Laravel Package

Product Decisions This Supports

• Do not adopt for Laravel or new PHP products. This is a deprecated Symfony bundle for DunglasApiBundle, not a Laravel package. It does not support current Laravel conventions, and its dependency chain is effectively obsolete.
• Build vs. buy: build on maintained API tooling instead. If the product needs LoopBack-style Doctrine ORM filtering, evaluate current API Platform filters, Laravel query-builder/filter packages, or a small internal filtering layer rather than reviving an archived bundle.
• Roadmap implication: exclude from strategic architecture. With zero dependents, no release since 2015, and archived status, it should not influence roadmap commitments or vendor selection.
• Use-case validation only. The underlying product idea—declarative, LoopBack-like filtering over Doctrine entities—can inform requirements for API filtering, but the package itself is a reference pattern, not a dependency.
• Feature scoping input. If customers request flexible API query filters, treat that as a product requirement to be satisfied by maintained ecosystem components, not by adopting this package.

When to Consider This Package

• Only as a historical reference when studying how LoopBack-style filters were mapped to Doctrine ORM in legacy Symfony/DunglasApiBundle applications.
• Only in a legacy Symfony codebase that already depends on DunglasApiBundle and cannot yet migrate, and even then only with explicit risk acceptance for an archived, unmaintained dependency.
• Never for Laravel. The package is not Laravel-native and does not fit Laravel’s HTTP, Eloquent, or service-container conventions without disproportionate integration work.
• Look elsewhere for any production use. Prefer maintained API Platform filters, Laravel-native query filtering, or an internal implementation when requirements include security, maintainability, PHP version support, or long-term ownership.
• Avoid when compliance, security patching, or vendor support matters. Archived status, 2015 release history, and zero dependent projects make it unsuitable for supported products.

How to Pitch It (Stakeholders)

Summary: This package is not a viable dependency for our Laravel/PHP roadmap. It is a deprecated Symfony bundle last released in 2015, archived, with no dependent projects and only 22 GitHub stars. It addresses an interesting product capability—flexible LoopBack-style filtering over Doctrine ORM—but the implementation is tied to obsolete Symfony/API tooling and carries unmaintained-code risk.

Recommendation: Do not adopt or budget for integration. If API filtering is a roadmap requirement, fund a small, maintained implementation using current framework-native tools or evaluate active API Platform/Laravel filtering packages. Engineering should treat this repository as a design reference only.

Executive framing: Adopting it would create technical debt, security exposure, and hiring/maintenance burden for negligible reuse value. The product need is legitimate; this package is not the delivery vehicle.