- Can I use pgs-soft/restfony-bundle in a Laravel application?
- No supported path exists. It is a Symfony 3 bundle that relies on Symfony bundle registration, the DI container, and compiler passes, none of which Laravel provides. Laravel's Eloquent, route model binding, FormRequests, and API Resources are incompatible with its abstractions. Treat it as a reference implementation rather than a dependency.
- Which Symfony and PHP versions does Restfony Bundle support?
- It targets Symfony 3.x and its associated PHP generation, which is end-of-life. Symfony 3.4 security support ended in November 2021, so adopting it means running an unpatched framework baseline. Porting to Symfony 5 or 6 would likely require rewriting service definitions, type hints, and serializer contracts.
- Is Restfony Bundle actively maintained?
- There is essentially no adoption signal: roughly 6 GitHub stars and 0 dependents. There is no community hardening, security-response process, or visible production use. You should assume it is unmaintained unless you verify recent commits and releases yourself.
- What license is Restfony Bundle released under?
- GitHub reports NOASSERTION because it could not detect a license file. That is a legal gate, not a footnote, since the actual terms are unknown until a human reads the repository. Do not ship it in a commercial codebase until the license text is confirmed.
- What dependencies does Restfony Bundle pull in?
- It is built around the Symfony-era REST stack, including Doctrine ORM and likely FOSRestBundle and JMSSerializer, plus a paginator such as Pagerfanta or KnpPaginator. Several of those transitive dependencies have their own EOL branches. Audit the full Composer dependency tree before considering adoption.
- Does Restfony Bundle generate CRUD endpoints for Doctrine entities?
- Yes, its value proposition is generic CRUD controllers attached to an entity to provide list, show, create, update, and delete endpoints with serialization and pagination handled by convention. That can accelerate internal admin APIs in a Symfony 3 application. It is less useful if you need custom authorization, validation, or non-standard resource shapes.
- Is Restfony Bundle safe to use in production?
- Risk is high. It is unmaintained, carries an ambiguous license, and targets a framework generation that no longer receives security patches. Generic CRUD bundles that hydrate entities directly from request payloads are a classic mass-assignment and IDOR surface. Any adoption requires a security review of how request data binds to entities and how queries are scoped.
- How do I install Restfony Bundle with Composer?
- In a Symfony 3 project you would require pgs-soft/restfony-bundle and register the bundle in AppKernel, then configure Doctrine and the REST stack. In Laravel there is no supported installation path, because a service provider will not bridge the DI, routing, and serialization differences. Do not attempt to force it into a Laravel app.
- What should Laravel developers use instead of Restfony Bundle?
- Use Laravel-native primitives: API Resources for serialization, FormRequests for validation, route model binding, policies and gates for authorization, and packages such as Laravel Sanctum or Passport for auth. For CRUD scaffolding, consider maintained Laravel packages or generate your own controllers. The pattern of one controller per resource is easy to reproduce without the dependency.
- How does Restfony Bundle compare to Laravel API Resources?
- They solve the same problem with incompatible abstractions. Restfony provides generic Symfony controllers tied to Doctrine entities, while Laravel API Resources transform Eloquent models into JSON responses. Restfony cannot be layered onto Laravel because it depends on Symfony HttpKernel-adjacent machinery. The honest comparison is conceptual, not functional.