- Is ntarakan/rest-bundle compatible with Laravel?
- No. Despite being described as a Laravel/PHP REST helper, the package is a Symfony bundle: its DependencyInjection, Configuration and Extension classes depend on the Symfony FrameworkBundle and Kernel, which Laravel does not run. Laravel consumes individual Symfony components such as HttpFoundation and Routing, but it has no bundle registration path and no equivalent of config/bundles.php. Do not add it to a Laravel composer.json expecting working CRUD endpoints.
- How do I install ntarakan/rest-bundle?
- In a Symfony application you would install it with composer require ntarakan/rest-bundle and register it in config/bundles.php, then import its routing and configuration. There is no service provider, facade or config publish step for Laravel, so no Laravel installation instructions exist. Before installing anywhere, read its composer.json to confirm the PHP and Symfony version constraints resolve against your project.
- What does ntarakan/rest-bundle actually do?
- It is a thin convenience layer that adds conventions and helpers around routing, controllers and JSON responses so CRUD endpoints stay consistent. The stated goal is less boilerplate for RESTful APIs. All of that surface is already covered first-party by Laravel resource controllers, Route::apiResource, JsonResource and Form Requests, and by Symfony routing plus the Serializer.
- Which PHP and Symfony versions does this bundle support?
- The package appears to be of Symfony 2.x/3.x vintage, so expect constraints that conflict with PHP 8.x and Symfony 5 or later. You must verify the exact require block in its composer.json before any spike, along with PSR-4 autoload correctness and transitive dependency age. Treat a Composer resolution conflict as a hard stop rather than working around it with --ignore-platform-reqs.
- Can I write an adapter to use ntarakan/rest-bundle in Laravel?
- You could port its conventions onto Laravel routing and controllers, but at that point the adapter is the actual deliverable and the dependency adds nothing. Porting a Symfony bundle's DI, configuration and routing conventions into Laravel's container essentially means reimplementing the behaviour natively. For any gap this package seems to fill, use Laravel's own API Resources, resource routes and Form Requests, or a maintained Composer package with real adoption.
- What is the maintained alternative to this bundle for REST APIs?
- In Laravel, use Route::apiResource with resource controllers, JsonResource and ResourceCollection for serialization, and Form Requests for validation and HTTP status handling. In Symfony, FOSRestBundle is the sane substitute if a bundle is mandatory, since it is maintained and widely adopted. Either native stack is strictly superior on support cost and framework upgrade effort.
- Is ntarakan/rest-bundle actively maintained?
- The health signals are poor: roughly one star, zero dependents, a very low package score, and no visible release cadence or CI evidence in the metadata. A single maintainer with no stated governance or security policy means a bus factor of one. Assume no bug reports, patches or security triage will arrive from upstream.
- What are the risks of depending on an unmaintained Symfony bundle?
- Framework lock-in is the biggest one: an unmaintained bundle pins your Symfony minor and patch range and blocks upgrades, a cost that typically surfaces six to twelve months after adoption. Any CVE in its transitive dependencies becomes your problem, with no upstream triage. The opportunity cost is also high because the problem is already solved first-party in both Laravel and Symfony.
- I have a legacy Symfony app that already uses this bundle. How do I migrate off it?
- Inventory every route and controller that relies on the bundle's conventions, then map each one to native Symfony routing, Serializer configuration and explicit HTTP status handling. Retire the bundle behind an upgrade ticket so the work is tracked, and add regression tests around the affected endpoints before removing the dependency. This reverse migration path is the realistic route, since inbound adoption is not recommended.
- Is it safe to use ntarakan/rest-bundle in production?
- Not recommended for new Laravel or Symfony work. Zero downstream usage means no bug reports, no patches and no security response, so you own all of that risk yourself. Permit evaluation only for a legacy Symfony codebase already shaped by the bundle's conventions, and only with a named owner, a fork strategy and a patch SLA.