patchlevel / event-sourcing-dashboard-bundle

1.0.0 2026-09-06 09:15 UTC

Requires

• php: ~8.2.0 || ~8.3.0 || ~8.4.0 || ~8.5.0
• patchlevel/event-sourcing: ^3.8.0
• patchlevel/event-sourcing-bundle: ^3.7.0
• symfony/asset: ^5.4.33 || ^6.4.1 || ^7.0.1 || ^8.0.0
• symfony/asset-mapper: ^6.4.1 || ^7.0.1 || ^8.0.0
• symfony/config: ^5.4.31 || ^6.4.0 || ^7.0.0 || ^8.0.0
• symfony/dependency-injection: ^5.4.33 || ^6.4.1 || ^7.0.1 || ^8.0.0
• symfony/expression-language: ^5.4.33 || ^6.4.1 || ^7.0.1 || ^8.0.0
• symfony/http-kernel: ^5.4.33 || ^6.4.1 || ^7.0.1 || ^8.0.0
• symfony/routing: ^5.4.33 || ^6.4.1 || ^7.0.1 || ^8.0.0
• symfony/var-dumper: ^5.4.29 || ^6.4.0 || ^7.0.0 || ^8.0.0
• twig/twig: ^3.20.0

Requires (Dev)

• infection/infection: ^0.32.0
• patchlevel/coding-standard: ^1.3.0
• phpstan/phpstan: ^2.1.32
• phpstan/phpstan-symfony: ^2.0.8
• phpunit/phpunit: ^11.5.45
• roave/security-advisories: dev-master
• wnx/commonmark-markdown-renderer: ^1.6

MIT

• Daniel Badura
• David Badura

• symfony
• bundle
• dashboard
• event-sourcing
• patchlevel

Published on Packagist.org on 2026-09-07 08:35 UTC

README

Event-Sourcing-Dashboard-Bundle

"A dashboard to inspect your events, time travel through your aggregates and manage your subscriptions."

Features

• Browse the raw event store and filter by aggregate, id, stream or event
• Inspect a single aggregate: its events, serialized state, snapshot and a full state dump
• Time travel through an aggregate to see its state at any playhead
• List all registered events together with their listeners and subscribers
• View and control subscriptions: boot, run, pause, reactivate, rebuild or remove
• Customize how events are rendered with the #[Inspect] attribute
• and much more...

Installation

composer require --dev patchlevel/event-sourcing-dashboard-bundle

Documentation

• Latest Docs
• Related Blog

Screenshots

Dashboard

Store

Inspector

Subscriptions

Events

Integration

• event-sourcing
• event-sourcing-bundle

Contributing

We are open to contributions as long as they are in line with our BC-Policy.

In addition to the general policy, the following rules apply to this bundle:

• Twig templates are not covered. Symfony allows overriding the templates of a bundle, but our templates, their names, blocks and variables can change in any release without notice.
• Controller internals are not covered. The controller classes, their methods and signatures are considered internal. The routes they serve (route names and paths) are covered by the BC-Policy.

Also note that the composer.lock is always generated with the newest supported PHP version as this is the version our tools run in the CI.