triadev/laravel-dev-config

Release historydanger

There has been only one release, published about nine years ago, with no releases in the last 12 months. This is strong evidence of a stagnant project for a dependency that may need compatibility updates.

Repo commit activitydanger

The repository had zero commits and zero active maintainers in the last three months, consistent with a project that has not been maintained since its initial release. This materially raises abandonment and compatibility risk.

Maintainerscaution

Only one registry account has publish access. That is a limited publishing base for this independently owned project and increases continuity risk if that maintainer stops maintaining it.

Project backingcaution

The registry namespace and repository owner match, and the repository owner is an individual account rather than an organization. This supports repository ownership alignment but offers limited backing capacity.

Repo issue activitycaution

There are no open issues or pull requests and no recent issue activity. This is consistent with inactivity, although it does not by itself show unresolved defects.