- Is micayael/commands-bundle a Laravel package?
- No. Despite appearing in a Laravel/PHP package feed, it is a Symfony2+ bundle built around Symfony's bundle conventions, including a Bundle subclass, a DependencyInjection extension, and compiler passes. Laravel has no bundles.php, no Kernel::registerBundles(), and no Extension mechanism, so the bundle's wiring layer does nothing on a Laravel stack. Treat it as Symfony source material, not a Laravel dependency.
- Can I install micayael/commands-bundle in Laravel 10 or 11 with Composer?
- Composer may resolve and install the package, but Laravel's package discovery will not register its Symfony bundle extension or wire any commands automatically. There is no path where you add it to composer.json and it just works under Artisan. Plan to manually register individual command classes or port their logic into app/Console/Commands.
- What console commands does micayael/commands-bundle actually provide?
- The bundle ships a set of reusable Symfony console command classes intended for scaffolding, inspection, and management from the CLI. The exact command list must be read from the repository's Command directory, since the README excerpt does not enumerate it here. Produce a one-line capability summary per command and compare each against stock Artisan before deciding whether any is worth keeping.
- How do I register its command classes with Laravel Artisan?
- If a command class extends Symfony\Component\Console\Command\Command and does not pull from a Symfony container, you can instantiate it in a service provider and register it with $this->commands([...]) or Artisan::starting(). Anything coupled to Symfony DI, config trees, or bundle parameters will fail on that path. For coupled commands, rewrite the logic as a Laravel-native command with $signature, $description, and handle() instead.
- Does micayael/commands-bundle support PHP 8.2 and Laravel 10/11?
- The Symfony2+ description dates the codebase to roughly 2015–2017, which implies PHP 5.6/7.0 constraints, older Symfony Console APIs, and likely no CI. Expect problems with removed functions and implicit-nullable parameters under PHP 8.2/8.3, plus signature drift against Symfony 6/7 Console. Laravel version support is moot because the bundle is not a Laravel package; test any extracted command in isolation first.
- Is micayael/commands-bundle actively maintained?
- Signals are uniformly negative: 0 stars, 0 dependents, a maintenance score of 2.53/5, and no visible release cadence. That points to a bus factor of one and little recent activity. Check commits, tags, issues, and CI status from the last 12 months before relying on it for anything operational.
- Is it safe to run unvetted CLI code from this bundle in production?
- CLI commands often touch the filesystem and may invoke shell processes, so unvetted third-party code carries real risk. There is no visible evidence of a security audit for shell injection or unsafe file operations. Review the sources or vendor a single reviewed class into app/Support rather than pulling the whole bundle as a dependency.
- How do I migrate the useful parts of this bundle into Laravel?
- Follow an extract, not install, sequence: inventory each command, triage it as duplicate, portable, or coupled, then port useful logic into app/Console/Commands using $signature, $description, handle(), and constructor injection of Laravel services. Preserve the MIT header and attribution in a NOTICE file. If a command is genuinely nontrivial and tightly bound to Symfony internals, vendor that single class with a thin wrapper instead of the bundle.
- What license does micayael/commands-bundle use, and can I copy its code?
- The repository is MIT licensed, so copying and adapting the command sources into your own application is permitted with the license notice retained. The MIT license removes legal friction but not engineering risk, since you still own any ported code. Keep attribution in a NOTICE file and treat the port as first-party maintenance going forward.
- What are the alternatives to this bundle for Laravel CLI scaffolding?
- Stock Artisan make:* commands, Laravel Prompts for interactive input, and small custom commands usually cover the same ground in about thirty lines each. Symfony Console helpers are also available directly because Laravel already bundles symfony/console. Compare every bundle command against these before taking on a fork or an adapter.