Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Footprints Laravel Package

kyranb/footprints

Kyranb/footprints is a lightweight Laravel package for tracking user activity. Add a trait to your models, record footprints through a polymorphic relationship, and query activity history with familiar Eloquent syntax—useful for audits and recent-activity feeds.

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • Audit trail / activity history features: Footprints provides a lightweight, opinionated way to record who created, updated, or deleted an Eloquent model. Use it to answer "who changed this record and when?" for customer-facing activity feeds, admin audit views, or compliance-lite requirements.
  • Build vs. buy (or rather, build vs. adopt): If your roadmap includes per-model change attribution, this package replaces a bespoke polymorphic activities table plus observer boilerplate with a maintained, tested dependency. Scope the decision against richer alternatives if you need field-level diffs, retention policies, or tamper-evident logs.
  • Laravel upgrade planning: The 3.2 release adds Laravel 13 support. This is a strong signal that the package is actively maintained and can be carried into your next framework upgrade cycle without blocking it — relevant if you're sequencing a Laravel 12 → 13 migration and inventorying dependencies for compatibility.
  • Roadmap de-risking: A maintained dependency with current-framework support reduces the "we'll have to fork or replace this" risk that often argues against adopting small single-maintainer packages.
  • Not a decision driver: This release contains no new product capabilities, so it should not change prioritisation of audit-related features — only the technical feasibility and upgrade timeline.

When to Consider This Package

Adopt when:

  • You need simple attribution ("user X performed action Y on model Z") rather than full change history.
  • Your models are standard Eloquent models and you're comfortable adding a trait/observer to each tracked model.
  • You're on, or planning to move to, a supported Laravel version — 3.2 explicitly covers Laravel 13, alongside the previously supported versions.
  • You want a small, readable dependency you could reasonably fork or vendor if maintenance lapses.
  • Your data volume is moderate and a single footprints-style table is an acceptable storage model.

Look elsewhere when:

  • You need field-level diffs, before/after values, or rollback — use a dedicated audit/versioning package (e.g. an activity-log or model-history library) instead.
  • You have compliance or tamper-evidence requirements (immutable logs, cryptographic chaining, long retention, export to a SIEM). Build or buy a dedicated audit system; a per-model trail package won't satisfy auditors.
  • You need high write throughput on hot tables — evaluate indexing and write amplification, or move logging out of the request path.
  • Bus factor matters more than convenience: this is a single-maintainer package. The 3.2 release shows activity, but plan for the possibility of taking ownership.

How to Pitch It (Stakeholders)

For executives: We're evaluating a small open-source Laravel component that records who changed what in our application. It gives us audit and activity-history capability with minimal engineering effort, and its latest release confirms it supports the newest Laravel version — so adopting it does not create an upgrade blocker. Cost is essentially engineering time to integrate, not licence spend. Main risk: it is maintained by a single author, and it is a lightweight log rather than a compliance-grade audit system; if we ever need regulatory-grade audit trails, we would need a different solution.

For engineering: Footprints (v3.2) is a trait/observer-based audit trail for Eloquent models, writing attribution rows to a dedicated table. The 3.2 release is a compatibility release adding Laravel 13 support — no API changes, no breaking changes, no deprecations. That makes it a low-risk dependency to trial: integrate behind a trait on two or three high-value models, verify query overhead and table growth under realistic volume, and confirm we're comfortable owning a fork if upstream stalls. Recommend a time-boxed spike rather than a broad rollout, and a decision gate on whether our audit requirements stay at "attribution" or escalate to "full change history" — the latter would mean a different package or an in-house design.

Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
novasa/laravel-language-center
opencage/geocode
adolfoholzer/parameters
livenetworks/ln-starter
shitoudev/permissionmanager
johannesclimacus/laravel-tui
hocvt/seotools
vitalybaev/sypexgeo
amphibee/themosis-ignition
gito-me/fast-excel
frankyso/laravel-ipaymu
geolize-studio/laravel-chile
boomerangui/chat
cgv/localized-resource
noith/settings
kda/laravel-package
kda/filament-dynamic-navigation
bypersoft/signbox
pairus/product-data
fayne/laravel-filament-cms-core