Weave Code
Crud Bundle Laravel Package
prezent/crud-bundle
prezent/crud-bundle is a PHP bundle for scaffolding CRUD workflows, helping developers generate create, read, update, and delete screens with less boilerplate. It targets admin panels and data-management interfaces, simplifying routine entity handling and rapid backend prototyping.
Easy CRUD for Symfony
Frequently asked questions about Crud Bundle
- Is prezent/crud-bundle compatible with Laravel?
- No. prezent/crud-bundle is explicitly a Symfony bundle and depends on Symfony-only primitives such as bundles.php/Kernel registration, the DependencyInjection container with compiler passes and tagged services, the EventDispatcher, and typically HttpKernel, Form, Validator, and Doctrine. There is no meaningful architectural fit for a Laravel application short of bridging a Symfony kernel, which adds more infrastructure than the CRUD abstraction saves. For Laravel, use resource controllers with form requests and policies, or a maintained admin panel.
- How do I install prezent/crud-bundle?
- The typical flow is composer require prezent/crud-bundle, enable the bundle in config/bundles.php (or the Kernel for older Symfony), import its configuration, and wire its routing. The repository metadata does not document these steps or any configuration reference, so confirm the exact setup with the maintainer or a spike before adding it to a real application. Also check the composer.json constraints first, because a bundle pinned to an older Symfony major will not install cleanly.
- What Symfony and PHP versions does prezent/crud-bundle support?
- The supported Symfony and PHP versions are not stated in the available metadata, and the composer.json constraint set could not be verified. A single-maintainer bundle with no dependents often lags current Symfony majors, so read composer.json and the last tag before adopting. If it does not support your target Symfony version, the package is a non-starter regardless of features.
- Does prezent/crud-bundle generate code or provide runtime services?
- The metadata does not make this clear, but CRUD bundles commonly generate concrete controllers, forms, and templates into your application rather than providing runtime services. If that is the case here, the generated code becomes your code the moment you use it, and the dependency is effectively one-directional and hard to remove. Ask the maintainer directly, and if generation is involved, isolate all generated artifacts in a dedicated namespace so they can be replaced file by file.
- How does prezent/crud-bundle compare to EasyAdmin or SonataAdmin?
- It is a thin convenience layer, whereas EasyAdmin and SonataAdmin are mature back-office frameworks with larger communities, active maintenance, and third-party security scrutiny. prezent/crud-bundle has 2 stars, 0 dependents, and no visible CI or release cadence, which is a poor signal next to those alternatives. The bundle is only worth considering as a prototyping accelerator for internal, low-risk admin screens.
- Does prezent/crud-bundle work with Doctrine ORM, and what about ODM?
- The bundle appears aimed at Doctrine ORM, since that is the standard persistence layer for Symfony CRUD tooling, but ODM or multi-driver support is not documented. Its assumptions about entity base classes, identifiers, and naming conventions are also unknown. Verify these against your domain model before committing, because conforming entities to undocumented mapping conventions is a common source of rework.
- How does prezent/crud-bundle handle validation, CSRF, and authorization?
- Validation, CSRF protection, authorization/ACL, and mass-assignment handling are not described in the available metadata, and those are the security-relevant seams of any CRUD layer. Do not expose generated CRUD screens to untrusted users until you have confirmed how input is validated, how access is checked, and whether request data can bind to sensitive entity fields. For customer-facing or regulated flows, treat the bundle as unsuitable until a security review says otherwise.
- Is prezent/crud-bundle actively maintained and safe to adopt?
- The available signals are poor: 2 stars, 0 dependents, an opportunity score of 0.07, and no indication of recent tags, commits, or issue triage. With a single maintainer and no downstream consumers, there is no field testing, no community pressure to keep Symfony constraints current, and no third-party security review. MIT licensing at least gives you the fork option, which is the only durable mitigation if you proceed.
- Is there a test suite and CI for prezent/crud-bundle, and how should I evaluate it?
- The metadata shows no evidence of a test suite or CI pipeline, so you cannot assume the bundle is verified against your target Symfony version. Run a short spike: install it in a throwaway Symfony app, generate a representative CRUD screen, and check compatibility, security defaults, and upgrade paths. Keep the exit strategy defined before the first integration, ideally isolating generated code in a dedicated module.
- What are Laravel alternatives to prezent/crud-bundle for CRUD scaffolding?
- For Laravel, skip this package and use the framework's own primitives: resource controllers, form requests for validation, policies and gates for authorization, API resources for serialization, and migrations/Eloquent for persistence. If you want an admin panel, choose a maintained Laravel-native package rather than bridging a Symfony bundle. This keeps the stack coherent and avoids an infrastructure layer that costs more than the boilerplate it removes.
Weaver
How can I help you explore Laravel packages today?