- Is k3ssen/generator a Laravel package?
- No. Despite being filed in Laravel package listings, k3ssen/generator is a Symfony 4 bundle (GeneratorBundle) registered in config/bundles.php and built on Symfony's DI container, Symfony Console and Doctrine. There is no Laravel service provider, no Artisan command registration and no Eloquent support, so none of it is Laravel-native.
- Can I install k3ssen/generator in a Laravel application?
- Not practically. Even if Composer resolves the dependency, the bundle will not boot inside a Laravel app because Laravel never registers Symfony bundles or loads the bundle's DI service definitions. Making it work would require a Symfony kernel, which Laravel does not provide.
- Why does composer require k3ssen/generator fail on Laravel 10 or 11?
- The bundle pins Symfony 4.x components, Doctrine 2.x and PHP constraints around 7.1 to 7.3, while Laravel 10 and 11 ship Symfony 6/7 components and typically run on PHP 8.1 or newer. Those requirements collide and Composer reports conflicting constraints. Forcing resolution with ignore-platform-reqs gives you a broken dependency graph rather than a working install.
- What does k3ssen/generator actually generate?
- It scaffolds Doctrine entities and CRUD layers, including controllers, forms, repositories and Twig templates, derived from entity metadata and your database schema. Generation is driven by Symfony Console commands and outputs Symfony conventions rather than Laravel or Eloquent conventions.
- Is k3ssen/generator still maintained?
- No. The last release was 2019-10-20 with no commits in roughly six years, 2 stars, zero dependents and a single maintainer. Symfony 4 reached end of security support in November 2023, and there is no security response process or CVE triage. Treat it as abandoned.
- Does k3ssen/generator support PHP 8?
- Its composer constraints target the PHP 7.1 to 7.3 era, so installs on PHP 8.1 and newer will hit conflicts. Nothing in the repository indicates testing or support on modern PHP runtimes. Plan on assuming hard incompatibility.
- How does k3ssen/generator compare to Laravel's Artisan make commands?
- Laravel already ships make:model, make:controller, make:request and stub publishing, which cover most of the same scaffolding ground. The conceptual model of command-driven generation from templates overlaps, but no code is shared and Laravel uses .stub files rather than Twig templates. Laravel's tooling is first-party, maintained and Eloquent-aware.
- Can I reuse k3ssen/generator's templates or generation logic in a Laravel project?
- Partially. The stub templates and the field-type-to-template mapping rules can be read as a design reference, but they are coupled to Symfony DI, Doctrine metadata and Twig. Realistically you would rewrite them as Artisan make:* commands using Laravel's stub publishing, after a short spike in an isolated Symfony 4 container to judge the generated output.
- What should I use instead for CRUD generation in Laravel?
- Start with Laravel's built-in Artisan generators plus your own make:* commands and published stubs tailored to your schema. If you need more, evaluate actively maintained Laravel scaffolding or CRUD packages rather than a six-year-old Symfony bundle. The demand for scaffolding tooling is real; this specific artifact is not the answer.
- Is k3ssen/generator safe to run in production?
- It is unmaintained, depends on an end-of-life Symfony 4 stack, has a bus factor of one and no security process. At most, run it once in a throwaway legacy Symfony container as a one-off scaffolding experiment. Never make it a production dependency in a Laravel application.