Weave Code
Dashboard Bundle Laravel Package
kalamu/dashboard-bundle
Kalamu Dashboard Bundle is a Laravel package for adding a ready-made admin dashboard to your app, with configurable pages, widgets, and management screens that help you scaffold back-office UI faster while keeping the implementation in PHP.
Configurable Bootstrap dashboard for Kalamu
Frequently asked questions about Dashboard Bundle
- Is kalamu/dashboard-bundle a Laravel package?
- No. Despite being surfaced by Laravel-oriented package heuristics, kalamu/dashboard-bundle is a Symfony bundle built for the Kalamu CMS. Its release notes reference upgrading compatibility with Symfony 4 and dropping Symfony 2, with no mention of Laravel, service providers, Blade, or the extra.laravel manifest key. It ships Twig templates and Bootstrap 4 markup, so nothing in it targets Laravel's container, routing, or view layer.
- Does kalamu/dashboard-bundle work with Laravel 10 or 11?
- No. Laravel 10 and 11 require PHP 8.1 or newer and Symfony 6/7 components, while this bundle caps out at Symfony 4.x, which reached end of life in November 2023. There is no auto-discovery, so Composer would not register anything for a Laravel app. Making it run would require a hand-written service provider plus a full port of the Twig views, which is a rewrite rather than an integration.
- Can I use kalamu/dashboard-bundle as a scaffold for a Laravel admin dashboard?
- Only as a design reference, not as a dependency. The reusable value sits in Twig templates and a configuration schema, not in portable PHP domain logic you could shim into a Laravel package. If you want the layout and navigation ideas, read the templates and rebuild them in Blade with your own middleware and policies. Budget days for a design reference versus weeks for a genuine port.
- How do I install kalamu/dashboard-bundle?
- Installation follows the Symfony bundle flow: add the package with Composer, register the bundle in your kernel or bundles.php, and publish its assets and configuration. There is no Laravel package:discover step and no php artisan vendor:publish command provided by the package. In practice you can only complete these steps inside a legacy Symfony 4 application, not a Laravel one.
- Which Symfony and frontend versions does kalamu/dashboard-bundle support?
- The ceiling is Symfony 4.x, with the latest release explicitly adding Symfony 4 support and dropping Symfony 2. Frontend assets target Bootstrap 4, which still depends on jQuery for its interactive components. That means a consumer on Bootstrap 5 or Tailwind inherits a parallel legacy asset pipeline rather than a small styling delta. The package cannot coexist with Symfony 5.4, 6, or 7 constraint sets.
- Is kalamu/dashboard-bundle still maintained?
- The last release dates to March 2020, leaving the project roughly five years dormant at the time of review, and the most recent change was a framework floor raise with no feature content. There is a single maintainer and no published security-fix language. Because the supported Symfony branch is itself end of life, even a future compatibility bump would arrive years behind the current major.
- What are the security risks of running this dashboard bundle in production?
- An admin dashboard is an authentication-adjacent, highest-privilege surface, and the package's authorization and output escaping are unaudited by any third party. Layering that on an unpatched Symfony 4.4 branch means framework-level vulnerabilities would go unfixed as well. If you inherit a legacy Kalamu deployment, put a security review budget against the admin routes before exposing them. For most teams the safer answer is not to adopt it at all.
- What are good Laravel alternatives for a ready-made admin dashboard?
- For Laravel specifically, look at Filament, Laravel Nova, Backpack, Orchid, or Voyager depending on whether you want a code-first panel, a paid product, or a CRUD generator. All of them support current Laravel releases, ship Blade or Livewire views, and integrate with Laravel's authorization gates and policies out of the box. Any of these closes the scaffolding gap this Symfony bundle was being evaluated for.
- Can I fork kalamu/dashboard-bundle and port it to Laravel?
- Technically yes, but the cost is a rewrite rather than a port. You would replace Twig with Blade, rebuild the routing, middleware, and gate integration against Laravel's kernel, migrate the Bootstrap 4 and jQuery assets to your own pipeline, and reimplement the config schema as a Laravel config file. Since the bundle carries no PHP domain logic to preserve, most teams find it faster to start from a maintained Laravel admin package.
- Who actually uses kalamu/dashboard-bundle?
- There is very little adoption signal: around three GitHub stars and zero dependents in the Composer ecosystem. The package exists to support Kalamu CMS deployments rather than general-purpose Laravel or Symfony back offices. Unless you have a hard vendor or legacy Kalamu requirement, treat it as an artifact of a specific CMS rather than a library to build on.
Weaver
How can I help you explore Laravel packages today?