Weave Code
Backend Tools Bundle Laravel Package
modera/backend-tools-bundle
Modera Backend Tools Bundle is a PHP/Symfony bundle that equips admin backends with ready-made tooling: configurable grids and filters, CRUD scaffolding, forms, and UI helpers. It reduces boilerplate so teams can ship maintainable management panels faster.
[READ-ONLY] Provides "Tools" section for backend.
Frequently asked questions about Backend Tools Bundle
- Is modera/backend-tools-bundle a Laravel package?
- No. Despite being catalogued alongside Laravel/PHP packages, it is a Symfony bundle built for Modera's own backend admin panel. It relies on Symfony bundle kernels, DI extensions and compiler passes, YAML/XML container configuration, Twig, and Modera's menu-contribution registry, none of which exist in Laravel. There is no service provider, facade, or Artisan surface to hook into.
- Can I install modera/backend-tools-bundle in a Laravel 10 or Laravel 11 application?
- Not as a viable dependency. The package declares Symfony 2.8/3.x-era constraints and PHP 5.5-7.0-era syntax, and it has no Laravel integration points. Forcing it into a Laravel 10/11 app would be a greenfield port rather than an integration. The practical answer is to use it only as a behavioral reference and reimplement the small feature surface natively.
- What does Modera Backend Tools Bundle actually provide?
- It supplies reusable utilities for Modera's Symfony-based backend and admin interfaces, including configurable grids and filters, CRUD scaffolding, forms, UI helpers, and a Tools section with operations utilities such as cache clearing and environment/version introspection. The functional surface is relatively small and mostly commodity admin tooling. It is not a standalone admin panel and depends on ModeraBackendBundle and ModeraFoundationBundle.
- Which PHP and Symfony versions does modera/backend-tools-bundle support?
- The last release dates to 2016-06-10 and targets the PHP 5.5-7.0 era with Symfony 2.8/3.x APIs, annotation routing, and older Twig. It predates Symfony 4 entirely and would need meaningful rework for Symfony 5/6, let alone a modern PHP runtime. Assume incompatibility with current Laravel and Symfony stacks.
- Is modera/backend-tools-bundle still maintained?
- No meaningful maintenance signal exists. The last release was in June 2016, roughly nine years ago, and the repository is a read-only monorepo subtree split where issues and pull requests are not the development channel. It has zero stars, zero dependents, and no downstream validation. Treat it as dormant and unsupported unless you confirm an active upstream monorepo and commercial support.
- What are the security concerns with running this bundle in production?
- The bundle exposes privileged admin tools such as cache and configuration introspection and potentially log or file access, which are classic information-disclosure and CSRF targets. The code is unpatched and pulls unpinned, unpatched Modera/Symfony dependencies into your application. Running it in a modern app means accepting vulnerabilities without maintenance. Confirm licensing and provenance before any further evaluation.
- How would I implement the Tools section natively in Laravel?
- Read the bundle's controllers, routing.xml, Contributions, and Twig templates to enumerate each tool, its inputs, authorization check, and side effects. Then build a small first-party package with a route group under your admin prefix, auth and can middleware mapped to existing gates, Blade views, CSRF on every mutation, and Artisan commands backing destructive actions. That likely amounts to only 50-150 lines of native Laravel code. Extracting cache maintenance into a deploy-pipeline service is the highest-value artifact.
- Does the bundle have a Laravel service provider or publishable configuration?
- No. It is a Symfony bundle that registers services through DI extensions and compiler passes and is configured via YAML or XML container files. There is no Laravel service provider, facade, config publishing, or Artisan command surface. Any Laravel configuration you see would have to be written from scratch.
- What is the best migration path from this bundle to Laravel?
- Start with a short discovery phase to document each tool's action, required permission, destructive or non-destructive nature, and audit expectations. Then reimplement in Laravel as a small first-party package rather than vendoring Symfony 2-era code. Do not port partial code, because that buys the vulnerabilities without the maintenance. If discovery shows the utilities are just table stakes like clearing cache and showing versions, consider dropping the capability.
- Are there Laravel alternatives for admin panel tooling like grids, CRUD scaffolding, and filters?
- Yes. Rather than porting a Symfony bundle, evaluate Laravel-native admin packages or build a small first-party admin tool package tailored to your gates and deployment pipeline. Common options in the Laravel ecosystem include Filament, Laravel Nova, Backpack, and Orchid, though you should assess them against your own authorization and audit requirements. For a handful of operations utilities, a custom package is often simpler and safer than adopting a framework.
Weaver
How can I help you explore Laravel packages today?