Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Dashboard Bundle

Dashboard Bundle Laravel Package

kunstmaan/dashboard-bundle

Dashboard bundle for the Kunstmaan CMS on Symfony, adding a configurable admin dashboard with analytics, statistics and widget blocks that surface key site metrics at a glance. Small and low-activity; intended for existing Kunstmaan projects rather than standalone use.

View on GitHub
Deep Wiki
Context7

KunstmaanDashboardBundle adds a configurable dashboard layer to Symfony applications as part of the Kunstmaan CMS bundle suite. It lets you assemble dashboards from reusable widgets, each rendered as a self-contained service, giving administrators an at-a-glance overview of the data that matters to them.

  • Widget-based dashboard composition via tagged services
  • Configurable per-user or per-role layouts
  • Ready-to-use widgets plus a base class for custom ones
  • Twig-rendered templates with overridable views
  • Integrates with the Kunstmaan admin UI and security layer
Frequently asked questions about Dashboard Bundle
Can I use kunstmaan/dashboard-bundle in a Laravel application?
No. It is a Symfony bundle built for Kunstmaan CMS, with a Bundle subclass, DI extension, compiler passes, and Twig overrides that Laravel's container and view layer do not load. Laravel does not boot Symfony bundles, so even forced Composer resolution would register nothing. Treat the code as a reference for the pattern, not as a drop-in dependency.
What is kunstmaan/dashboard-bundle used for?
It adds a customizable admin dashboard to Kunstmaan CMS, with widget-based panels for quick access to key information. It includes a widget registry, dashboard pages, per-user layout persistence, and a Google Analytics integration. It is a CMS plugin, not a general-purpose PHP dashboard library.
Is kunstmaan/dashboard-bundle still maintained?
No. The last release was 2014-07-29, and the repository has roughly 4 stars and zero dependents, with no active maintainer. There is no path to upstream security patches, so any fork becomes your permanent responsibility. It is effectively abandoned.
Which Laravel and PHP versions are compatible with kunstmaan/dashboard-bundle?
None. Its Composer constraints target the Symfony 2.x and PHP 5.4 to 7.0 era, which hard-conflicts with Laravel 10 or 11 on PHP 8.2 and newer. Compatibility is not just about version constraints: Laravel would not boot the bundle at all.
Does the Google Analytics widget in kunstmaan/dashboard-bundle work with GA4?
No. The bundle's headline Google Analytics integration targets Universal Analytics and the Core Reporting API v3, which Google sunset; UA stopped processing data in July 2023. Against GA4 the analytics widget is non-functional regardless of framework. You would need to replace it with google/analytics-data or a Matomo Reporting API adapter.
How do I build a customizable widget dashboard in Laravel?
Reimplement the bundle's concepts natively. Define a DashboardWidget interface and bind a widget registry as a singleton, render widgets with Blade components or Livewire, store per-user layouts in an Eloquent model with a JSON column, cache analytics responses with Cache::remember and a queued refresh job, and gate dashboards with authorization policies. Laravel already provides every primitive the bundle invented for Symfony.
How long does it take to port kunstmaan/dashboard-bundle to Laravel?
Roughly 3 to 5 developer-days for the framework layer: widget contract, registry, Blade or Livewire rendering, and layout persistence. The analytics adapter is separate work and depends on whether you target GA4, Matomo, or internal metrics. Migrating old Twig views and Bootstrap markup adds time if you reuse the visual design.
What are the Laravel alternatives to kunstmaan/dashboard-bundle?
For admin dashboards, Laravel Nova, Filament, and custom Livewire dashboards cover the same ground with active maintenance and Laravel-native authorization, routing, and views. If you need a widget registry specifically, a small custom singleton plus Blade components is usually less work than adopting a full admin panel. The bundle itself is not a realistic alternative in Laravel.
Is kunstmaan/dashboard-bundle safe to run in production?
It is high risk. The package is abandoned, era-locked to old Twig syntax and Bootstrap 2/3 markup, and likely pins a stale google/apiclient with known CVEs. There have been no upstream patches for roughly 11 years. If you must use the code, audit it for deprecated crypto, hardcoded credentials, and unsafe HTML handling before trusting it.
What license does kunstmaan/dashboard-bundle use, and can I fork it?
It uses the MIT license, which permits forking, porting, and commercial redistribution with attribution. Licensing is the cleanest dimension of the package. Forking is legally fine, but you take on all long-term ownership and maintenance.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console
pnscripts/filament-broadquill-lite
pnscripts/laravel-sentfold-lite
vleap/mx-sdk-laravel-internal
twidpay/utils
htetmyathlaing/scout-elasticsearch-driver
artisan-toolbox/front-awesome
ls/client-assistant
users-au/laravel-client
cgv/localized-resource
noith/settings
kda/laravel-package
kda/filament-dynamic-navigation
bypersoft/signbox
pairus/product-data
fayne/laravel-filament-cms-core
nodisrupt/laravel-agent
sierratecnologia/media-manager