muhammadsaeedparacha/multi-tenant-laravel-acl

Release historydanger

The package has had no release in about 8 years and 10 months, with zero releases in the last 12 months. Its seven-release history shows an established artifact but not ongoing maintenance.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with the old last push and release history, this is strong evidence of abandonment risk.

Project backingcaution

The package and repository are owned by the same individual account, providing a clear ownership match but no organizational backing signal. This offers limited maintenance capacity when activity has already stopped.

Repo popularitycaution

The repository has one star, zero forks, and zero watchers. Low popularity is only supporting evidence, but it offers little community fallback for an inactive package.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. For an authorization package, this is a modest transparency and maintenance gap rather than a severe risk by itself.