- Is baskin/history-bundle a Laravel package?
- No. baskin/history-bundle is a Symfony bundle that wraps the Gedmo DoctrineExtensions Loggable listener with a Twig extension for rendering entity change history. It targets Symfony dependency injection, Doctrine ORM, and Twig templates, not Laravel service providers, Eloquent, or Blade. Treat it as a UX reference implementation rather than an installable Laravel dependency.
- Can I install baskin/history-bundle in a Laravel application with Eloquent?
- Not usefully. The package depends on Symfony and Doctrine event subscribers, while Laravel auditing typically relies on Eloquent observers or traits. Installing it would not give you history for Eloquent models unless you also introduced Doctrine ORM, which is an architecture-level change. For most Laravel apps, port the timeline and diff concept or use a Laravel-native auditing package instead.
- What does baskin/history-bundle actually do?
- It provides a Twig extension that renders change history recorded by Gedmo Loggable. The real auditing engine is Gedmo, a Doctrine event subscriber that writes entity changes into a log table such as ext_log_entries. The bundle is a thin presentation layer that helps templates display those revisions, not a standalone auditing system.
- How do I install and configure baskin/history-bundle in Symfony?
- The repository does not provide a verified installation guide in the available context, so treat any setup as needing source review. A Symfony project already using Doctrine and Gedmo Loggable would enable the Loggable listener, configure the log entry entity, and register the Twig extension. Confirm the declared Symfony, Twig, Gedmo, and PHP constraints before installing, because compatibility with Symfony 6 or 7 and Gedmo 3.x is unverified.
- Does baskin/history-bundle support Laravel 11 or PHP 8.3?
- There is no evidence of Laravel support at all, so Laravel 11 is not a supported target. The package's compatibility with PHP 8.2 or 8.3, Symfony 6 or 7, Twig 3, and Gedmo 3.x is also unverified in the provided assessment. Check composer.json constraints and run a compatibility spike before relying on it.
- What are the best Laravel alternatives to baskin/history-bundle for audit logs?
- For Laravel and Eloquent, owen-it/laravel-auditing and spatie/laravel-activitylog cover most revision-tracking and activity-log requirements. Both are Laravel-native and actively maintained, unlike this Symfony bundle. Choose laravel-auditing when you need field-level old and new values, and activitylog when you need a broader human-readable activity feed.
- How do I display field-level diffs instead of raw serialized history data?
- Gedmo Loggable stores changed fields in a data payload, and a presentation layer must hydrate that payload into readable field names and old versus new values. The available assessment questions whether this bundle does that or simply renders raw serialized data. In Laravel, store changed fields as JSON and render a Blade component that maps keys to labels and formats values. Always test with real entities before assuming the diff output is usable.
- Does baskin/history-bundle paginate or filter entity history?
- Pagination and filtering are not confirmed in the provided context. The assessment flags the risk that an entity's full log could be loaded per render, which becomes expensive because audit tables grow without bound. If you adopt the pattern, add server-side pagination, date and actor filters, and indexes on entity type, entity id, and timestamp. For Laravel, implement these in the repository or query scope behind your history view.
- Is baskin/history-bundle maintained and safe for production?
- The assessment rates it high risk and presumptively abandoned: zero stars, zero dependents, a single maintainer, no visible CI, and no release cadence. There is also no security disclosure path, which matters because audit logs concentrate confidential data. If you use it in Symfony, fork and vendor the code, assign an internal owner, and budget time for PHP and Symfony upgrades.
- How do I port baskin/history-bundle's history timeline concept to Laravel?
- Model an audits table with action, entity type, entity id, changed-fields JSON, actor id, and timestamp, or use laravel-auditing's table directly. Capture changes with Eloquent observers or an Auditable trait instead of Doctrine event subscribers. Recreate the Twig extension ergonomics as a Blade component and view composer that shows a timeline, field-level diff, and resolved actor name. Roll it out per entity, starting with the model that has the highest compliance or support value.