- Can I use sylius-labs/sensio-distribution-bundle in a Laravel application?
- No, not realistically. The package is a Symfony 2/3 Standard Edition artifact that expects an AppKernel, a bundles.php registration graph, and the Symfony console and Composer-script lifecycle. Laravel's extension model uses service providers, Artisan, and the laravel/laravel skeleton, which share none of those primitives. Loading it would require running a second kernel and container alongside Laravel's, which is a dual-bootstrap anti-pattern.
- How do I install sylius-labs/sensio-distribution-bundle with Composer?
- You would run composer require sylius-labs/sensio-distribution-bundle, but on a Laravel project that alone gets you nothing usable. The bundle still needs to be registered inside a Symfony kernel and driven by Symfony console commands. There is no service provider, config file, or Artisan integration shipped with it.
- What does sensio-distribution-bundle actually do?
- It adds Symfony console commands that automate installing and updating a framework distribution: running Composer, clearing caches, installing assets, and handling deployment steps. Its payload is essentially requirement checking, install-web scaffolding, and parameter generation. All of that is either trivially reimplementable in Composer scripts or already handled by laravel/installer and the Laravel skeleton.
- Is sylius-labs/sensio-distribution-bundle still maintained?
- No. The last release was March 2019, the repository has around 12 stars and zero dependents, and there is no active maintenance. There is also no disclosure channel and no realistic CVE-response path. Any vulnerability in its dependency surface is effectively permanently unpatched.
- What is the Laravel equivalent of SensioDistributionBundle or Symfony Flex?
- On Laravel the correct analogs are laravel/installer, the laravel/laravel skeleton, and composer.json post-create-project-cmd scripts. On Symfony the direct and maintained successor is symfony/flex. This bundle is superseded in both ecosystems, so there is no scenario where adopting it is the shortest path.
- Does sensio-distribution-bundle support PHP 8 and modern Symfony versions?
- No. Its runtime constraints target the PHP 5.5 to 7.x window and it is written against deprecated Symfony APIs such as KernelInterface constants and getParameter-era container access. Those symbols are removed in Symfony 6 and 7, and Doctrine, Console, and Filesystem peer constraints all pin to obsolete majors. Reviving it would mean a multi-day compatibility shim for zero functional gain.
- Should I use this bundle instead of laravel/installer for project scaffolding?
- No. laravel/installer plus the skeleton and Composer scripts covers project scaffolding on Laravel without any extra dependency. The bundle's scaffolding is Symfony-specific and would need to be reimplemented to produce anything Laravel can boot. Keep the ticket closed against this package and use the framework-native tooling.
- How do I run install-time requirement checks in Laravel with Composer scripts?
- Add a small Composer script under post-create-project-cmd or post-install-cmd that validates PHP version, required extensions, and env values, then exits non-zero on failure. That is roughly 50 lines and gives you the same outcome the bundle's requirement checks provide. It stays inside Laravel's own tooling instead of pulling in a foreign kernel.
- Is sylius-labs/sensio-distribution-bundle safe to run in production?
- It is high risk. The code is unmaintained since 2019, depends on removed Symfony APIs, and has no security disclosure process, so fixes will not arrive. The MIT license is the only clean aspect of the package. There is no production scenario where running it is preferable to native Composer scripts.
- I am on Symfony Standard Edition. Should I fork this bundle or migrate?
- Migrate. The officially supported path since 2017 is Standard Edition to Symfony Flex, which is the maintained successor to this bundle's role. This bundle is a casualty of that migration, not a dependency of it, so scope the Flex migration separately and drop the bundle. Only consider a fork if you have an explicit, evidenced requirement that both Flex and Laravel's installer fail to meet.