luizhenriqueferreira/laravel-acl

Release historydanger

The package has only two releases, with the latest published over five years ago and none in the past five years. This is strong evidence of abandonment for a library that may need compatibility and security maintenance.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the past three months, consistent with the long release gap and leaving no recent maintenance evidence.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is not decisive, but these figures provide little supporting evidence of active community use or review.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools are configured. That weakens maintenance and vulnerability-detection evidence without proving the package is unsafe.

Security policycaution

The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency gap for a package that manages application access control.