Model or dataset
owen-it/laravel-auditing avatar
owen-it/laravel-auditing

laravel-auditing has one active support row and twelve EOL

Record the change log from models in Laravel

3,473 stars407 forksPHPMIT

At a glance

What is it?
A Laravel package that records Eloquent model changes through a trait, where the support table marks one of thirteen version lines active, writes PHP constraints with a space after the operator, and sends you to a second repository for the documentation.
Who is it for?
laravel-auditing is a reasonable pick when you need model level history that you can query yourself rather than sift through an application's own log files, since attaching a trait is the whole integration. Two things are worth checking first.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 13 days ago.
What is it written in?
Mainly PHP, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • owen-it/laravel-auditing3,473 ★ · +8
Star history
Repository2026-09-242026-11-15
owen-it/laravel-auditing3.5k3.5k

8 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

One row of thirteen is active, and it is the newest

The support table runs from 14.x down to 2.x, thirteen rows in all, and exactly one of them is not marked End of life. That row is 14.x, paired with Illuminate 11.x.x through 13.x.x and a PHP requirement written as 8.2 or newer, and its status cell is decorated with a rocket shortcode rather than being left plain. Everything else reads End of life, including 13.x. Note what that means for the pairing column: the active 14.x line starts at Illuminate 11, while the end of life 13.x line reaches back to Illuminate 7.x.x. The newest three releases are all on the active line, at v14.0.4, v14.0.5 and v14.0.6, so the table is not describing a project that still supports old framework versions on a maintained branch.

The PHP column is written with a space after the operator

Every row of the PHP Version column separates the comparison operator from the version with a space. The 14.x row reads `> = 8.2`. The 13.x and 12.x rows read `> = 7.3 | 8.0`, with a pipe for the alternative. The remaining rows step down through `> = 7.3`, `> = 7.2.5`, `> = 7.1.3`, `> = 7.0.13` and `> = 5.5.9`. Read as prose that is fine. Read as a constraint it is not, because a version comparison written with a space is not the form a package manager parses, and the pipe is not the separator that form uses either. Nothing in the page says the column is illustrative, so anyone copying a row out of the table to build a constraint has to rewrite it first.

The documentation lives in a different repository

The page describes the package in two sentences and then points outward. It says the package helps you understand changes in your Eloquent models by providing information about possible discrepancies and anomalies that could indicate business concerns or suspect activities, and that a trait keeps a history of model changes whose data is straightforward to retrieve and display. Everything else is a pointer: the documentation site at laravel-auditing.com, and a second repository named owen-it/laravel-auditing.com where the guide lives at `docs/guide/documentation.md`. The contributing link goes further still, to `http://laravel-auditing.com/docs/master/contributing`, which is an unencrypted address and a path segment named after a branch.

Four quality tools, two of which are formatters

The top level of the tree carries five configuration files for code quality, and they come from four different tools. `.pint.json` configures Pint, the formatter Laravel ships with. `.styleci.yml` configures StyleCI, the hosted formatting service that predates it. `.scrutinizer.yml` configures the static analysis service, and the page carries its build status badge. Then `phpstan.neon.dist` configures PHPStan and `phpunit.xml` configures the test runner. Having a formatter configured twice is the part that will surprise someone setting this up, since a Pint run and a StyleCI run can disagree about the same lines and the repository does not say which one wins. The rest of the tree is conventional: `composer.json`, `CHANGELOG.md`, `CONTRIBUTING.md`, `LICENSE.md` and a `tests/` directory.

Seven badges pointing at two destinations

The badge row at the top of the page has seven anchors and two distinct targets. Three of them are the same Scrutinizer build status URL for the master branch, written out three times, and three more are the same Packagist package URL, also three times. The seventh is a Discord invite link, the only destination in the row that is not a build status or a package listing. The duplicate anchors are harmless when they render as three different badge images, since each anchor is meant to wrap its own image, but they mean the row carries no more information than a single status link and a single package link would. What the row does establish is that the package is distributed through Packagist under the owen-it vendor name.

Migrations and stubs ship inside the package

The tree is laid out for a package that installs itself into an application. There is a `config/` directory, so configuration ships as a publishable file rather than being read from the package namespace. There is a `database/` directory, so the audit tables arrive as migrations the application runs. There is a `stubs/` directory, which is what a service provider copies from when an application needs generated files. Alongside them sit `src/` for the package code and `tests/` for its own suite, and `composer.json` ties them together under the namespace shown on the page as OwenIt\LaravelAuditing. The mechanism the page advertises is correspondingly small: attach a trait to a model and its changes are recorded, then read the records back.

Three patch releases in eight days, then nothing

The tag history is a tight cluster followed by a gap. v14.0.4 was published on 2026-06-12, v14.0.5 on 2026-06-18 and v14.0.6 on 2026-06-20, so three patches in nine days on the same minor line. The last commit to the default branch is dated 2026-09-18, roughly three months after that last tag, with no new release in between. The repository is not archived, so this is not a case of a finished project being left visible; it is a project whose releases stopped while its commits continued. For anyone pinning a version, the practical reading is that v14.0.6 is the newest published artifact and the master branch has moved past it.

The credited authors do not share the vendor namespace

The credits section names three people, Antério Vieira, Raphael França and Quetzy Garcia, each under a personal GitHub handle, followed by a link to all contributors. Underneath sits a heading reading Special thanks for keeping this project active, and three more names, Morten D. Hansen, erikn69 and parallels999. None of those accounts is the vendor the package publishes under: the repository is owen-it/laravel-auditing, the Packagist package is owen-it/laravel-auditing, and the namespace is OwenIt\LaravelAuditing. So the code sits under an organisation account while the people named as its authors and its maintainers are individuals elsewhere, and the page credits the individual accounts as the primary authors.

Editorial conclusion

laravel-auditing is a reasonable pick when you need model level history that you can query yourself rather than sift through an application's own log files, since attaching a trait is the whole integration. Two things are worth checking first. The version table is the guide to whether the line you install fits your framework: 14.x is the only Active support row and it starts at Illuminate 11, while everything from 13.x downward is marked End of life, so an older application is on an unmaintained line by the project's own reckoning. And the documentation is not in this repository at all, it lives in owen-it/laravel-auditing.com, so budget for a second place to look, because this page carries no install command of its own.

Frequently asked questions

What does laravel-auditing record?

It keeps a history of changes to your Eloquent models. Attaching a trait is the integration, and the package frames the resulting records as information about possible discrepancies and anomalies that could indicate business concerns or suspect activities. The audited data is meant to be retrieved and displayed by the application.

Which Laravel versions does laravel-auditing support?

The support table pairs 14.x with Illuminate 11.x.x to 13.x.x, and that row is the only one marked Active support. Every row below it, from 13.x down to 2.x, is marked End of life, with 13.x reaching back as far as Illuminate 7.x.x.

Which PHP version does laravel-auditing 14.x require?

The table's PHP Version column for 14.x reads > = 8.2. Older rows read > = 7.3 | 8.0, > = 7.3, > = 7.2.5, > = 7.1.3, > = 7.0.13 and > = 5.5.9, all written with a space between the operator and the version.

Where is the laravel-auditing documentation?

On laravel-auditing.com, or in the owen-it/laravel-auditing.com repository at docs/guide/documentation.md. The documentation is a separate repository from the code, and the contributing link uses a /docs/master/ path segment on an unencrypted address.

How do I install laravel-auditing?

The page gives no install command of its own and refers you to the documentation site and the docs repository for installation and usage. The package tree ships config/, database/ migrations, stubs/, src/ and tests/, and it is distributed on Packagist as owen-it/laravel-auditing.

How is laravel-auditing licensed?

Under the MIT license, with a LICENSE.md file at the root of the repository. The namespace used by the package is OwenIt\LaravelAuditing, and the vendor name on Packagist is owen-it.

Official sources

  1. License: MIT
  2. owen-it/laravel-auditing on GitHub
  3. Project website
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/owen-it-laravel-auditing.svg)](https://hysenlabs.com/projects/owen-it-laravel-auditing)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/owen-it-laravel-auditing.svg)](https://hysenlabs.com/projects/owen-it-laravel-auditing)

Was this useful?