Filament Activity Log Laravel Package

Product Decisions This Supports

• Build vs. buy for audit/compliance surfaces. This package turns Filament's admin panel into an audit control center out of the box: tenant-scoped activity resources, widgets, timelines, exports, investigation filters, and retention controls. The buy case is strong anywhere a compliance, security, or customer-support team needs to answer "who changed what, when, and from where" without your team owning that UI.
• Roadmap sequencing for compliance-adjacent features. Tamper-evident HMAC signatures, integrity verification and backfill commands, retention holds that block pruning, and safe restore/revert with conflict detection map directly onto SOC 2 / ISO 27001 / GDPR-style control requirements. If those are on the roadmap, this release collapses several quarters of "audit hardening" work into an upgrade.
• Enterprise and multi-tenant readiness. The central tenant-aware query boundary applied consistently across resources, widgets, filters, exports, timelines, pruning, and mutations is the headline product decision: it makes the package defensible as a per-tenant audit surface rather than a single-tenant admin toy. That unlocks upmarket tiers and B2B deals where tenant data isolation is a contractual requirement.
• Security posture as a product differentiator. Destructive actions disabled by default, explicit authorization on mutations and exports, secret redaction in display/export paths, and sensitive attributes excluded from restore/revert are defaults you can cite in security questionnaires and enterprise procurement reviews.
• Incident response and support workflows. Request ID and IP investigation filters, persisted risk scores, and high-risk tabs turn the activity log from a passive record into a triage tool — useful for support escalation, abuse investigation, and post-incident review without building internal tooling.
• Operational trust and diagnosability. The filament-activity-log:doctor command plus integrity verification gives ops a self-serve health check, reducing escalation load on engineering for "why is the audit log broken/empty/slow" tickets.
• Platform/upgrade planning. The compatibility matrix (PHP 8.3–8.5, Laravel 12–13, Filament 4–5, Spatie Activitylog 4–5) is a forcing function on your own upgrade cadence — adopting v2 means committing to the modern stack and retiring older PHP/Laravel/Filament combinations.
• Localization-driven market expansion. Twelve fully translated locales with automated key/placeholder parity tests support launches in EMEA, LATAM, and APAC markets without per-locale fork maintenance.

When to Consider This Package

Consider adoption when:

• You run Filament 4 or 5 on Laravel 12/13 and PHP 8.3+, and Spatie Laravel Activitylog is already (or plausibly) your audit backbone. v2 is explicitly built for that stack; there is no path for older Laravel/PHP/Filament versions.
• You need an auditable record that withstands scrutiny — tamper evidence, retention holds, and verified integrity — rather than a casual "recent changes" list.
• You operate multi-tenant admin panels where showing one tenant another tenant's activity is an unacceptable failure mode.
• You want authorization, redaction, and destructive-action safety to be defaults, not per-project customizations you must re-implement and re-audit each release.
• Your team would otherwise build and maintain activity resources, filters, exports, restore/revert logic, and retention tooling in-house — the maintenance and security-review cost of that bespoke code usually exceeds the integration cost here.
• You have compliance or procurement pressure (security questionnaires, enterprise customer audits) that benefits from a documented, tested security posture with automated PHPStan level 8, Pint, dependency auditing, and a CI release matrix.

Look elsewhere or defer when:

• You are still on Laravel ≤11, PHP ≤8.2, or Filament ≤3, or you cannot yet move off Spatie Activitylog 3 — v2 does not support those combinations.
• You are not using Filament. The package's value is overwhelmingly the Filament UI layer; the underlying log store is Spatie's, which you can adopt directly.
• You need a general-purpose, panel-agnostic audit pipeline with custom sinks (SIEM streaming, data-warehouse export, immutable WORM storage). This package is a Filament control center, not a log-shipping product; pair it with a dedicated pipeline if those are hard requirements.
• Your audit volume is enormous and write-heavy. v2 improves large-table performance with indexed metadata and scope-safe aggregate caching, but you should benchmark against your retention window and query patterns before committing.
• You have a strict "no major-version churn" policy and cannot absorb the v1→v2 migration (audit metadata migration, backfill, and changed security defaults) in the current cycle.

Upgrade risk to flag explicitly: v2 flips security defaults — destructive actions are off by default, mutations and exports now require explicit authorization, and stale reverts are blocked. Teams upgrading from v1 should expect previously working admin actions to be denied until policies and gates are reviewed. The upgrade path (vendor:publish migrations → migrate → backfill → verify-integrity → doctor) should be run in staging first and treated as a security-relevant change requiring sign-off, not a routine composer update.

How to Pitch It (Stakeholders)

For executives: This upgrade converts our admin activity log from a nice-to-have audit trail into a security-first audit control center — with tamper-evident signatures, tenant isolation, retention holds, and risk scoring. It directly supports the compliance and enterprise-procurement questions we keep answering manually, and it is a mature, widely adopted package (100,000+ downloads) rather than bespoke internal code we would have to build, secure, and maintain. The cost is an upgrade project, not a new platform.

For engineering: v2.0.0 is a major release with breaking changes. The migration is a one-time sequence — publish migrations, migrate, backfill audit metadata, verify integrity, run doctor — and the security defaults have intentionally tightened: destructive actions are disabled by default, mutations and exports require explicit authorization, stale reverts are blocked, and sensitive/system attributes and configured secrets are excluded or redacted. Expect existing policies and gates to need review so legitimate admin workflows aren't locked out. In exchange we get a consistent tenant-aware query boundary across every package-owned query, indexed audit metadata and scope-safe aggregate caching for large tables, localized domain exceptions with structured logging context, and first-class extension points (audit rules, context collectors, timeline sources, subject restorers). Compatibility targets PHP 8.3–8.5, Laravel 12–13, Filament 4–5, and Spatie Activitylog 4–5, with CI across the release matrix, PHPStan level 8, Pint, and dependency auditing — so adopting v2 also pins our own upgrade cadence to that stack.

Recommended next step: run the v2 upgrade in staging behind a feature flag, execute doctor and verify-integrity as acceptance gates, and audit which admin actions are newly denied before scheduling production rollout.