Package Health/ezappslab/laravel-evolver

ezappslab/laravel-evolver

Laravel Evolver appears usable and reasonably healthy for dependency adoption: it has a recent stable release history, active development through the latest release, a non-archived organization-owned repository, clear MIT licensing, substantial documentation, and extensive tests in both the artifact and repository. The main risks are its short 112-day history, zero observed repository popularity, complete concentration of recent commits in one contributor, absence of security scanning and a security policy, and use of a post-autoload-dump lifecycle script. These concerns warrant monitoring and review of release changes, but the available evidence does not indicate abandonment or severe supply-chain unfitness.

Latest 2.1.0

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Lifecycle scripts

A post-autoload-dump install lifecycle script is present. This adds execution surface during installation and merits review, although the signal does not show a dangerous script by itself.

Maintainers

Only one registry account has publish access. This is partly mitigated by the repository being organization-owned, so it is a publishing-resilience concern rather than a severe ownership risk.

Release history

The package is young at 112 days with five releases and a median interval of about 19 days, including a release on August 29, 2026; this shows active iteration but limited long-term maturity.

Repo bus factor

All 22 recent commits came from one contributor. Organization ownership provides some ability to hand off maintenance, but the observed activity remains fully concentrated.

Repo commit activity

There were 22 commits in the last three months and one active maintainer, showing strong recent activity but no evidence of a broader maintenance bench.