Filament Logger Laravel Package

Product Decisions This Supports

• Build vs. buy for audit logging: Avoids a custom Filament audit UI (resource, searchable filters, structured diffs, saved tabs, date presets, CSV/JSON exports, dashboard widgets, auth/event logging, redaction, pruning). A from-scratch equivalent is plausibly 1–3 sprint-weeks plus ongoing maintenance; this package compresses the first version to an install-and-configure exercise.
• Compliance and enterprise-readiness roadmap: Supports SOC 2 / ISO 27001-style evidence needs, customer security questionnaires, GDPR accountability, and incident-response workflows by making admin activity reviewable and exportable. It is an audit-trail enabler, not a compliance certification.
• Security and insider-risk features: Enables review tabs for high-risk actions and auth issues, alerts for destructive actions, and accountability for “who changed what, when.” Useful for support escalations, disputed changes, and post-incident reconstruction.
• Feature scoping: Decide whether to expose raw diffs to non-technical admins, which fields must be redacted, which events are “high risk,” retention windows, and alert routing to mail/Slack/Discord. The package supplies defaults; the PM still owns policy.
• Roadmap sequencing: Good candidate for a compliance-blocking milestone or enterprise deal unblocker. Lower priority if the product has no admin panel, no regulated customers, and no internal audit requirement.
• Use cases to validate: admin activity review, security investigations, support “who changed this record?”, filtered audit exports for auditors/customers, alerting on destructive actions, and custom domain-event logging without building a separate audit surface.

When to Consider This Package

Consider it when:

• The product runs Filament 3.x, 4.3.1+, or 5.x on Laravel 11/12/13 and PHP 8.2+. Enforce the Filament 4.3.1 floor because earlier 4.x releases were affected by an upstream security advisory.
• You need a Filament-native audit/activity UI quickly and are willing to build on spatie/laravel-activitylog.
• You need searchable diffs, exports, saved review tabs, date presets, dashboard widgets, auth-event logging, notification logging, redaction, and retention pruning without custom UI work.
• You can accept community-maintained OSS risk and mitigate it: pin versions, add integration tests, review upgrades, and optionally maintain an internal fork.
• Your audit volume is modest-to-moderate and fits the activitylog database model, with pruning configured for retention.
• You already have, or are willing to add, clear authorization rules around who can view audit data.

Look elsewhere when:

• You need enterprise-grade audit infrastructure: immutable/WORM storage, cryptographic tamper evidence, legal hold, multi-year retention, real-time SIEM streaming, or vendor SLAs/indemnities.
• Procurement or security policy blocks packages with low adoption signals — 26 stars and 0 dependents is a real due-diligence flag, even if code quality badges look good.
• You lack Laravel/Filament capacity to vet, configure, test, and maintain a community package.
• Your audit needs extend beyond Filament/admin activity into broad application, infrastructure, or non-Filament surfaces.
• You require complex multi-tenant isolation, ABAC, or regulatory controls beyond the package’s recipes and defaults.
• You need supported versions outside the stated matrix, especially Filament versions below the 4.3.1 security floor.

How to Pitch It (Stakeholders)

For executives: This is a low-cost, MIT-licensed accelerator for audit readiness and admin accountability. It gives us a reviewable audit trail, exportable evidence, and high-risk-action alerting inside the Filament admin panel without a custom build. It supports security questionnaires, incident response, and enterprise customer expectations. The main risk is ecosystem maturity: low adoption and community maintenance mean we should pilot it, pin versions, and keep an exit path. Recommended decision: approve a time-boxed staging pilot with clear success criteria before committing it to a regulated or customer-facing workflow.

For engineering: It is a thin Filament UI and logging layer on top of the well-established Spatie activitylog package. It provides a ready-made resource, filters, diffs, exports, widgets, auth/model/resource/notification logging, redaction, and pruning. It has tests, PHPStan, docs, changelog, and a CI compatibility matrix, but it is community-maintained and low-adoption, so treat it as a dependency to pin and monitor. Pilot checklist: install in staging, verify supported Filament/Laravel versions, test redaction and authorization, validate exports and retention, measure query performance at expected volume, and document fork/upgrade ownership.