- Is kitlabs/kit-generator-bundle a Laravel package?
- No. Despite being filed under a Laravel/PHP slot, it is a Symfony bundle: the name ends in Bundle and it extends SensioGeneratorBundle. Laravel has no bundle system; it uses service providers and Artisan. There is no service provider, facade, or extra.laravel discovery entry in this package.
- Can I install kitlabs/kit-generator-bundle in a Laravel app?
- Not usefully. Composer may fail because it pulls Symfony 2/3-era constraints against a modern Laravel app on PHP 8.1+ and Symfony 6/7. Even with forced resolution or --ignore-platform-reqs, nothing registers the bundle in Laravel's kernel, so no Artisan commands appear. You would get dead weight plus supply-chain surface.
- What Laravel versions does kitlabs/kit-generator-bundle support?
- None. There is no Laravel version support because the package is built for Symfony's bundle and DI container, and it depends on the end-of-life SensioGeneratorBundle. Symfony replaced that generator with MakerBundle in Symfony 4. For Laravel, use native Artisan make commands or custom stubs.
- How do I install kitlabs/kit-generator-bundle?
- In a Symfony 2.7–3.4 app, install via Composer and register the bundle in AppKernel, then use its console commands. In Laravel there is no supported install path: no service provider, no config publishing, and no Artisan command registration. Do not treat a successful composer require as integration.
- What does kitlabs/kit-generator-bundle actually generate?
- It layers kit scaffolding—code, config, and assets packaged as reusable templates—on top of SensioGeneratorBundle's generator. The output follows Symfony conventions such as bundles, Doctrine entities, and annotations. It does not generate Laravel conventions like Eloquent models, migrations, or form requests.
- Why doesn't kitlabs/kit-generator-bundle work with php artisan?
- Laravel's console is Artisan, built on symfony/console but bootstrapped through Laravel's kernel and service providers. This bundle registers through Symfony's AppKernel and DI container, which Laravel never loads. Its commands are Symfony console commands tied to the bundle, not Artisan commands. Without a rewrite onto Artisan stubs, nothing shows in php artisan.
- Is kitlabs/kit-generator-bundle maintained?
- Maintenance risk is high. The repository shows 5 stars, 0 dependents, no visible release cadence, CI, or security policy, and a composite score of 0.055. Zero downstream consumers means no validation against current frameworks and no one to triage issues. Its host SensioGeneratorBundle is EOL, so it is a dead branch off the Symfony upgrade path.
- What are the best Laravel alternatives for scaffolding and code generation?
- In Laravel, use artisan make:* commands, custom stubs, declarative generators like Blueprint, or admin-panel generators like Filament and Backpack. A small internal Artisan-stub generator is realistically 1–2 days of work and avoids a snowflake dependency. These options match Laravel conventions and are maintained.
- Can I use kitlabs/kit-generator-bundle in a legacy Symfony 2.7 or 3.4 project?
- It is only architecturally coherent there, and even then it is legacy. You would install it with Composer, register it in AppKernel, and use console commands in a Symfony 2.7–3.4 codebase. That is a framework-upgrade conversation toward MakerBundle, not a package to adopt for new work.
- Is kitlabs/kit-generator-bundle safe for production or CI use?
- No. It is dev-only convenience code that executes on developer machines and in CI with repository access, and low-star zero-dependent packages are a recurring abandoned-package takeover vector. Supply-chain risk is unquantified and transitive risk is high because it imports the EOL SensioGeneratorBundle. Prefer maintained, convention-aligned tooling.