Weave Code
Rest Bundle Laravel Package
gollumsf/rest-bundle
gollumsf/rest-bundle is a Symfony bundle for building RESTful APIs with less boilerplate. It helps configure resource endpoints, handle requests, serialize responses, and keep JSON API output consistent across services.
gollumsf/rest-bundle is a Symfony bundle for building RESTful APIs with a cleaner, convention-oriented structure. It helps keep controllers focused on application logic while supporting consistent request handling and JSON-friendly responses.
- Symfony-native integration through bundle configuration and services
- REST-oriented controllers for resource-based endpoints
- JSON response support for API-friendly output
- Lightweight setup for small services and prototypes
- A practical foundation for consistent API behavior
Frequently asked questions about Rest Bundle
- Is gollumsf/rest-bundle a Laravel package?
- No. It is a Symfony bundle and depends on Symfony's HttpKernel, bundle registration, compiler passes, and config-tree semantics, none of which exist in Laravel. Laravel's service container, routing layer, and middleware pipeline are not compatible surfaces for a Symfony bundle, and there is no bridge that makes one run inside the other. If your target stack is Laravel, this package is out of scope before any code is written.
- Can I install gollumsf/rest-bundle with Composer in a Laravel application?
- Composer may resolve the package, but resolving is not integrating. A Symfony bundle registers itself through the Symfony kernel and exposes no Laravel service provider, facade, or config publish step, so nothing in a Laravel app will autoload or boot it. There is no known reference implementation of this bundle inside Laravel, and with zero dependents there is no community path to follow.
- What license does gollumsf/rest-bundle use, and is it safe for commercial use?
- It is GPL-3.0, which is viral copyleft. Any proprietary product that distributes the bundle, including on-prem installs, appliances, SDKs, and white-label builds, inherits obligations most commercial legal teams will refuse. SaaS-only deployment is often argued to be defensible, but that is a legal determination rather than an engineering one, and it materially narrows where you can ship.
- What does gollumsf/rest-bundle actually do?
- It is a thin, opinionated helper for building Symfony REST endpoints: controller conventions, request and response handling, serialization, consistent error responses, and sensible defaults so JSON endpoints ship faster. The stated scope is a very simple REST API implementation, which signals a small surface area rather than a framework. Expect roughly a few hundred lines of response formatting and controller glue, not deep infrastructure.
- How do I get the same behavior natively in Laravel without this bundle?
- Laravel already covers everything this bundle advertises. Use Route::apiResource for CRUD routing, route-model binding for lookups, FormRequest for validation, JsonResource and ResourceCollection for serialization, and the exception handler for consistent JSON error shapes. A mid-level engineer reproduces the bundle's behavior with these primitives in under a day, with no new dependency and no license exposure.
- Which Laravel, Symfony, or PHP versions does gollumsf/rest-bundle support?
- That is unknown and unverifiable from the package metadata. PHP version constraints, Symfony major alignment, and transitive dependency pins are not surfaced, so any integration would likely pin your host application's Symfony minor version. That turns a convenience dependency into an upgrade ceiling, which is the opposite of what you want in a long-lived service.
- Is gollumsf/rest-bundle actively maintained and safe for production?
- Treat it as high risk. There is one star, zero dependents, no vendor behind it, a bus factor of one, no security-response process, and no evidence of a test suite or CI. With no documented API contract there is nothing a technical lead can sequence an integration against, so it is not production-ready for a Laravel codebase.
- Why does gollumsf/rest-bundle show a 2026 release date?
- The recorded last-release timestamp is 2026-08-29, which is a future or invalid date. That means the scoring metadata itself is untrustworthy and the freshness signal cannot be used for upgrade or risk decisions. Treat any aggregate quality score as an upper bound until the anomaly is explained, either as a scoring-pipeline bug to escalate or a registry data problem.
- What are the best alternatives to gollumsf/rest-bundle?
- If your stack is genuinely Symfony, API Platform is the correct choice: actively maintained, permissively licensed, and with a real ecosystem. If your stack is Laravel, the alternative is Laravel itself, using API Resources, FormRequest, and apiResource routes. Either option avoids the GPL-3.0 obligation and the single-maintainer risk entirely.
- How would I integrate gollumsf/rest-bundle into a Laravel system if a stakeholder insists?
- Do not integrate it into the Laravel application. The only defensible pattern is an anti-corruption layer: run the bundle as a standalone Symfony service behind an HTTP boundary and call it from Laravel, which adds a second runtime, a second deployment, and a second security surface. The realistic sequence is legal review of GPL obligations, confirm the true target framework, run a one-day maximum spike at a container-level bridge, expect failure, and reject. That is strictly more cost and risk than reimplementing the endpoints natively.
Weaver
How can I help you explore Laravel packages today?