morcen/laravel-admin

Release historydanger

The package has had no releases in about 5 years and 3 months, despite 42 releases concentrated at its initial publication. That strongly raises abandonment and compatibility risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the long release gap. No provided maintenance signal compensates for this inactivity.

Repo popularitycaution

The repository has zero stars, forks, and watchers, so there is little visible community support to help identify or address problems. Popularity is supporting evidence rather than a verdict, and the maintenance signals already carry more weight.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. That weakens ongoing assurance, especially for a package that has not been maintained recently.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it is less significant than the prolonged inactivity.