shkiper/laravel-activity-log

Maintainerscaution

Only one account has registry publish access. The repository is user-owned rather than organization-backed, so there is little observed publishing redundancy if that maintainer becomes unavailable.

Release historycaution

The package has four releases, but none in the last 12 months and its latest release was about 17 months ago. This is meaningful evidence of slowing maintenance, although the repository remains active enough to avoid treating it as abandoned.

Repo commit activitycaution

The repository recorded no commits and no active maintainers in the last 3 months. Combined with the lack of recent releases, this points to reduced maintenance capacity.

Repo toolingcaution

Composer is used for builds, but no security scanning tools are configured. This is a transparency and maintenance-hygiene gap, not evidence that the package is unsafe.

Security policycaution

The repository has no security policy. That weakens vulnerability-reporting transparency for a package that records application activity, though it is not an abandonment signal by itself.