esign/laravel-database-auditing

Maintainerscaution

Only one registry account has publish access, which creates some operational concentration risk. The organization-owned repository provides partial backing, so this is a caution rather than a severe concern.

Release historycaution

The package has four releases over about three years, with one release in the last 12 months and a median interval of roughly 346 days. This is slow but not abandonment evidence because version 1.3.0 was released recently.

Repo commit activitycaution

There were zero commits and zero active maintainers in the last three months. The same-day release and repository push show recent publishing, but they do not demonstrate sustained development capacity.

Repo toolingcaution

The repository uses Composer but reports no security-scanning tools. The missing scanning is a maintenance hygiene gap, though it does not by itself make the package unfit.

Security policycaution

The repository has no security policy. That reduces transparency about vulnerability reporting and response expectations for a package that handles database auditing.