asvae/laravel-fixtures

Release historydanger

The package has four releases, all published in January 2017, with no releases in the last 12 months. This is strong evidence that maintenance has stopped.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the repository's last push in January 2017 and indicating abandonment risk.

Maintainerscaution

A single registry maintainer is consistent with a small user-owned project, but it provides little redundancy if that maintainer stops supporting the package.

Project backingcaution

The registry namespace and repository owner match, and the repository is owned by an individual rather than an organization. This supports identity continuity but provides no organizational maintenance capacity.

Repo issue activitycaution

There are no open issues or recent issue and pull request events. While a clean tracker is not inherently negative, here it provides no evidence of active maintenance.