Package Health/jeremykenedy/laravel2step

jeremykenedy/laravel2step

This is a generally healthy, established Laravel package: it has over eight years of release history, a stable latest major version, recent releases, a matching and maintained source repository, comprehensive repository tests, minimal runtime dependencies, and sensible security/build tooling. The main concerns are that recent commit activity is very low and concentrated in one contributor, the registry has only one publishing maintainer, and no security policy is present; these raise maintenance and response-risk concerns but are not outweighed by abandonment evidence because the repository is not archived, releases remain active, and recent pull requests were merged.

Latest v6.0.0

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

100

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publishing access, creating a modest release-continuity risk; this is registry access metadata rather than evidence that only one person maintains the repository.

Project backing

The repository is owned by an individual user rather than an organization, so there is no organizational backing to offset the concentrated contributor and maintainer base.

Repo bus factor

All one commit in the last three months came from a single contributor, making recent activity fully concentrated and increasing continuity risk; the repository is user-owned rather than organization-backed.

Repo commit activity

Only one commit was recorded in the last three months, so direct development activity is currently sparse and warrants caution; recent releases and merged pull requests provide partial compensating evidence.

Security policy

No repository security policy was found, which reduces transparency about vulnerability reporting and response procedures.