leafs/exception

Healthy and suitable to use, with a small maintenance-risk caveat. It has a long release history, a recent release, active commits, tests in the repository, and organizational backing; all recent commits come from one contributor and the repository lacks security scanning and a security policy.

Latest v5.0.2

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

All 17 recent commits came from one contributor, creating concentration risk; organizational backing provides some ability to hand maintenance off, but no second active contributor is evidenced.

Repo issue activity

There were no new issues or pull requests in the last month and no merged pull requests, so issue-based community activity is limited; the null open-issue count prevents a stronger conclusion.

Repo popularity

The repository has only 2 stars, 0 forks, and 1 watcher, indicating limited external adoption. This is supporting evidence rather than a decisive health problem because release and commit activity are strong.

Repo tooling

Composer is used as a build tool, but no security-scanning tools are configured, leaving a modest security-process gap.

Security policy

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