stephenlake/laravel-approval

Maintainerscaution

Only one registry account has publishing access, which creates some publishing continuity risk. The organization-owned source repository provides partial backing, so this is not severe on its own.

Release historycaution

The package has had no release in more than five years, despite eight total releases and a previously regular cadence. This is a meaningful maintenance concern for a framework integration.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months, consistent with the release history showing no registry release since December 2020. This is the strongest maintenance concern.

Repo toolingcaution

The repository uses Composer, but no security scanning tools were detected. That is a modest transparency and hygiene gap rather than evidence of abandonment.

Security policycaution

No security policy is present in the repository, leaving vulnerability-reporting expectations unclear. This is a minor concern because the repository is otherwise identified and maintained as a matching project.