ribafs/laravel-acl-exist

Release historydanger

The package has had no releases in the last 12 months, and its latest release was nearly six years ago. This strongly increases abandonment risk despite the stable version line.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, providing no evidence of current maintenance capacity.

Maintainerscaution

Only one registry account can publish releases, creating a thin publishing base. The linked repository is user-owned, so there is no organization backing shown to compensate for that concentration.

Repo popularitycaution

The repository has 0 stars, 0 forks, and 1 watcher, so there is little visible community activity or support capacity. Popularity is supporting evidence, but these values reinforce the maintenance concerns.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. This is a modest transparency and maintenance concern, especially for a package with no recent activity.