cloudcake/laravel-approval

Release historydanger

The latest release was in December 2020, nearly six years ago, and there were no releases in the last 12 months. This is the strongest evidence of stale maintenance, although the package has a stable release history rather than frequent failed releases.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with no registry release since December 2020, this materially raises the risk that compatibility issues will remain unaddressed.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, with three issues still open. This is a modest warning about responsiveness, but it is less significant than the release and commit gap.

Repo toolingcaution

The repository uses Composer build tooling, but no security scanning tool was detected. The missing scanner is a hygiene gap rather than evidence that the package is unsafe.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This lowers transparency modestly, though it is less consequential than the maintenance inactivity.