Weave Code
Activity Bundle Laravel Package
kitpages/activity-bundle
Kitpages ActivityBundle is a Symfony bundle for tracking and displaying user activity streams. It provides Doctrine-backed activity entities, services, and templates to log actions and render feeds, making it easier to add timeline or notification-style activity lists to an application.
Manages activities
Frequently asked questions about Activity Bundle
- Can I install kitpages/activity-bundle in a Laravel application?
- No. This is a Symfony bundle, not a Laravel package: it ships a bundle class, Doctrine ORM mappings, a Symfony EventDispatcher listener and Twig templates, with no service provider or Eloquent support. Its composer.json targets Symfony 2.x/3.x and an end-of-life PHP line, so a direct composer require will almost certainly collide with Laravel's symfony/* transitive constraints. Treat the repository as a design reference, not a dependency.
- What does kitpages/activity-bundle actually do?
- It records user activity streams: an actor performs a verb on an object, and each entry is persisted as a Doctrine entity you can query per user, object or context. A listener pushes entries from your own services, and Twig templates render the resulting timeline. The scope is deliberately small, roughly 300 to 600 lines of glue code for a news-feed or recent-actions widget.
- Is kitpages/activity-bundle still maintained?
- No. The last release was 2018-09-21, roughly seven years ago, with about 4 stars and zero dependents on Packagist. There is no evidence of PHP 8.2 or 8.3 support and no security response path. The MIT license is clean and permissive, but the lack of downstream usage means no incidental bug fixing or community-vetted edge cases.
- Does kitpages/activity-bundle support Laravel 10, 11 or 12 and PHP 8.2+?
- No. There is no Laravel 10, 11 or 12 support and no PHP 8.2+ declaration in the package metadata. The bundle is built on Symfony bundle conventions that Laravel does not load or resolve. Installing it into a modern Laravel app would fail on dependency resolution before any code ran.
- Why is the Doctrine ORM dependency a blocker for a Laravel project?
- Laravel's persistence layer is Eloquent, while this bundle fixes its storage contract to Doctrine-managed entity mappings and a bundle-defined schema. There is no adapter layer worth writing for a feature this small, and retrofitting Eloquent or a different store is a rewrite rather than a config change. Doctrine versus Eloquent is the hard boundary here.
- How would I implement this activity feed pattern natively in Laravel?
- Create an activities table, add an Activity model, and write a thin ActivityLogger service invoked from domain events with a queued listener so writes never block the request. Expose a paginated controller or API endpoint for reads and a Blade partial for rendering, keeping the read path separate from the write path. The whole port is roughly half a day of schema and model work. If a Symfony service genuinely exists in your estate, the MIT license lets you fork and vendor it, but budget a sprint for PHP 8 upgrades and a CI matrix.
- What database schema should an activity stream table use?
- Use uuid or id, actor_type and actor_id, verb, object_type and object_id, optional target_type and target_id, a JSON metadata column, and created_at. Add composite indexes on object_type, object_id, created_at and on actor_type, actor_id, created_at so scoped timeline queries stay fast. This mirrors the bundle's entity shape while staying native to Eloquent migrations.
- How do I render an activity feed in Blade instead of the bundle's Twig templates?
- Translate the Twig templates into a Blade partial that loops over a paginated collection of activity models. Keep the verb, actor and object formatting in a small presenter or model accessor rather than in the template itself. The bundle's templates are still useful as a rendering reference for layout and phrasing, even though the syntax does not carry over.
- Is kitpages/activity-bundle suitable for an audit log or compliance-grade activity history?
- No. It is a lightweight UI feed primitive with no immutability guarantees, retention policy or compliance tooling. An audit-grade log needs append-only storage, tamper evidence and a defined retention schedule, none of which this bundle provides. If audit or regulatory requirements are in scope, it is disqualified entirely.
- What maintained Laravel alternatives exist for activity feeds and activity logs?
- For a lightweight UI feed, a native Eloquent implementation is usually the best fit given how small the feature is. For broader activity logging, maintained packages such as spatie/laravel-activitylog are commonly used, and owen-it/laravel-auditing suits audit-trail style requirements. Benchmark those against your exact requirement, feed versus event-sourced history, before committing.
Weaver
How can I help you explore Laravel packages today?