Package Health/jeroennoten/laravel-adminlte

jeroennoten/laravel-adminlte

This release appears suitable to depend on, with strong evidence of maturity, transparency, and ongoing project activity: the package has existed for over 10 years, has 123 releases, six releases in the last 12 months, a stable non-prerelease version, a matching and package-referencing repository, extensive documentation, repository tests, and recent merged pull requests. The main concerns are that no commits or active maintainers were recorded in the last three months, repository security scanning is absent, the security policy is missing, and workflow permissions are not consistently least-privileged. These are meaningful governance and maintenance cautions, but they do not outweigh the package's long release history, recent release activity, repository structure, and lack of deprecation or dangerous workflow patterns.

Latest v4.0.0

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by an individual account rather than an organization, so the project has less institutional backing and may be more dependent on the individual maintainer.

Repo commit activity

No commits and no active maintainers were recorded in the last three months, which is a maintenance caution; this is partly offset by the six recent package releases, recent repository push, and 11 merged pull requests in the last month.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected, leaving a security-process and maintenance-transparency gap.

Security policy

The repository has no security policy, reducing transparency about vulnerability reporting and response expectations.

Token permissions

One workflow lacks top-level permissions and another declares top-level write permissions, so workflow privilege hardening is inconsistent and warrants review.