Nova Auditing User Fields Laravel Package

Product Decisions This Supports

• Build vs. buy for audit logging: This package is an integration layer over laravel-auditing, so the real decision is whether audit trails are a core differentiator (build) or commodity compliance infrastructure (buy/adopt). The 0.2.0 release reinforces the "buy" case by tracking upstream — the package maintainer absorbs framework and dependency churn rather than your team.
• Compliance and traceability roadmap: Supports decisions around "who changed what, when" requirements — SOC 2 evidence, GDPR data-change records, internal incident forensics, and customer-facing change history. Audit logging is usually a checkbox requirement; a maintained package keeps that checkbox cheap.
• Framework upgrade planning: 0.2.0 adds Laravel 7 support and moves to laravel-auditing v10. This is a signal for roadmap sequencing: the package is now viable for teams on Laravel 7 (and presumably 5.8–6.x, given the dependency bump) but gives no forward signal past Laravel 7. Factor this into upgrade-train planning and treat the package as a lagging indicator of framework support.
• Dependency hygiene decisions: The laravel-auditing v10 bump is a major-version dependency change. PMs should confirm it's paired with any breaking changes in the audit storage schema or API surface before committing to it in a release; this affects whether adoption is a same-sprint task or a scoped migration.

When to Consider This Package

Adopt when:

• You need model-level audit trails in a Laravel app and don't want to own the diffing, storage, and retrieval logic yourself.
• You're on Laravel 7 (and, depending on the dependency constraints, earlier 5.x/6.x versions) — 0.2.0 explicitly targets that range.
• Your team is comfortable pinning laravel-auditing v10 and accepting its major-version cadence as a transitive risk.
• Audit requirements are standard (CRUD change history, actor attribution, revert capability) rather than highly bespoke.

Look elsewhere or wait when:

• You're on Laravel 8+ or planning to move soon — 0.2.0 stops at Laravel 7, and there's no stated forward-compatibility commitment. Verify against the package's constraint file rather than release notes alone.
• You need audit events outside Eloquent (API gateways, queue workers, non-Laravel services) — you'd be better served by a dedicated event pipeline or a broader observability tool.
• You require tamper-evident or cryptographically chained audit logs for regulatory reasons; a general-purpose auditing package typically doesn't provide that guarantee.
• The wrapper adds little over using laravel-auditing directly — evaluate whether the convenience justifies an extra dependency in the chain.

Open questions to resolve before committing: exact supported Laravel/PHP matrix, migration path from laravel-auditing v9 to v10 (schema or config changes), and whether the package declares support for future Laravel majors. With a 0.2.0 version number, treat the API as pre-1.0 and expect churn.

How to Pitch It (Stakeholders)

To executives: Audit logging is a compliance and incident-response requirement we will need regardless of which product direction we take. This package is a thin, low-cost integration that lets us satisfy it without dedicating engineering to building change-tracking from scratch. The 0.2.0 release is a maintenance update — it adds Laravel 7 support and upgrades the underlying auditing library — which tells us the package is actively maintained. Risk is low and reversible: it's a library dependency, not an architectural commitment.

To engineering: Version 0.2.0 brings Laravel 7 compatibility and moves to laravel-auditing v10. Before we adopt, confirm the v9→v10 upgrade implications (config, migration, audit table schema) and check the package's declared version constraints, since it does not yet advertise support beyond Laravel 7. It's still a 0.x package, so expect breaking changes on minor bumps — pin the version and review release notes as part of our dependency routine. If the wrapper turns out to add little, we can drop to laravel-auditing directly with minimal rework.