- Is pitoune/report-bundle compatible with Laravel?
- No. pitoune/report-bundle is a Symfony bundle built on Sylius core, Doctrine ORM, and the Sylius resource/grid stack, so it offers no compatible surface for Laravel's container, Eloquent, or HTTP kernel. Running it under Laravel would require standing up a parallel Symfony/Doctrine runtime for a single feature, which is not a practical integration. For a Laravel application, implement reporting natively or choose a maintained Laravel package.
- What is pitoune/report-bundle used for?
- It is a lightweight Symfony bundle for defining reusable report logic, assembling data from application sources, rendering report output, and integrating reporting into Symfony services. It is intended for dashboards, admin panels, and scheduled report workflows inside a Sylius application. The bundle is a read-only subtree split of the Sylius reporting system.
- Can I install pitoune/report-bundle in a Laravel project with Composer?
- No, not on a modern Laravel skeleton. Its Composer constraints pin PHP 5.6/7.x, Symfony 2.8/3.x, Doctrine 2.x, and Sylius 0.x/early 1.x, so dependency resolution fails against Laravel 9–11 and PHP 8.2+. The only way to install it as-is is an isolated legacy container running PHP 7.4 with a compatible Sylius stack, which is not a Laravel integration.
- Which PHP, Symfony, and Sylius versions does pitoune/report-bundle require?
- Expect constraints around php ^5.6 || ^7.0, symfony/* ^2.8 || ^3.0, doctrine/orm ^2.5, and Sylius core ~0.x or ~1.0. None of those align with PHP 8.2+, Symfony 6/7, or Laravel 9–11. The last release was 2017-07-12, so there has been no compatibility update for modern runtimes.
- Is pitoune/report-bundle abandoned or still maintained?
- It is effectively abandoned. The last release was 2017-07-12, leaving roughly eight years without a commit, security review, or PHP/Symfony compatibility update. The repository is a generated, read-only subtree split, so patches cannot land under the pitoune/report-bundle name; fixes would have to go through upstream Sylius, which retired the reporting component.
- What are the production and security risks of using pitoune/report-bundle?
- The risk is high. Abandoned transitive dependencies from legacy Symfony, Doctrine, and Twig carry known CVEs with no advisories from this package, and the generated split has no accountable maintainer. Composer will flag the package as abandoned, and adopting it means owning security patching if you fork or vendor it internally.
- How do I configure pitoune/report-bundle for custom report formats?
- In Symfony, report definitions, data assembly, and renderers are wired through bundle configuration and services, and the extensible design supports custom formats and integrations. In a Laravel application there is no supported configuration path because the bundle expects Symfony and Sylius runtime services. If you need custom report formats in Laravel, build them with Laravel services, scheduled jobs, and an export layer instead.
- Can I test pitoune/report-bundle in a modern Laravel app or CI pipeline?
- No. A Composer install or runtime boot will fail on modern Laravel, PHP 8.2+, and Symfony 6/7 before meaningful tests can run. You can only test it in an isolated legacy PHP 7.4 container with the matching Sylius stack, and that does not validate it for a Laravel production target.
- What are the best alternatives to pitoune/report-bundle for Laravel reporting?
- For Laravel, reimplement the reporting concept natively using the query builder or Eloquent, a scheduled job, and an export service; the bundle's report definitions, renderers, and generation pipeline are small and not proprietary. You can also evaluate maintained Laravel reporting packages that support your PHP and Laravel versions. For Symfony, use Doctrine plus a maintained reporting library rather than this EOL Sylius component.
- Who maintains pitoune/report-bundle and where do I report issues?
- There is no accountable maintainer under the pitoune/report-bundle name. The repository is a read-only subtree split generated from the upstream Sylius monorepo, so issues must target Sylius, which no longer accepts reporting component issues. With 1 star and 0 dependents, there is no community, fork activity, or third-party validation to rely on.