leafs/sprout

Healthy and suitable to use, with a narrow maintenance base as the main caveat. It has frequent releases, active recent commits, tests, clear licensing, and organization backing, but relies on one active contributor and lacks a security policy.

Latest v5.1.1

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

All 21 recent commits came from one contributor, creating a genuine continuity risk; organization backing partly compensates because maintenance can be handed off within the organization.

Repo tooling

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

Security policy

The repository has no SECURITY.md or other detected security policy, reducing transparency about vulnerability reporting and response.

Token permissions

Both workflows lack top-level token permissions declarations. No workflow requests top-level write access, but explicitly declaring least-privilege permissions would be stronger hygiene.