Package Health/cryonighter/formula-doctrine

cryonighter/formula-doctrine

Usable with caveats: it has strong documentation, tests, licensing, and active recent releases, but all recent repository work comes from one contributor and the project has no security policy or scanning. Review its maintenance plan before making it a critical dependency.

Latest 1.4.0

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publishing access. This is not proof of poor maintenance, but it leaves release administration dependent on a single person.

Project backing

The registry namespace and repository owner match, but the owner is an individual user rather than an organization. This supports package identity while offering no organizational continuity beyond the current maintainer.

Repo bus factor

All 50 commits in the last three months came from one contributor, creating a significant single-person maintenance risk. The repository is user-owned rather than organization-owned, so there is no provided organizational backing to compensate for that concentration.

Repo issue activity

There are no open issues or pull requests, and no issue or pull-request activity in the last month. With active commits this is not abandonment evidence, but it provides little evidence of community support.

Repo tooling

Composer is used as a build tool, but no security-scanning tooling was detected. The missing scanner is a genuine transparency gap for a dependency library, though it does not outweigh the evidence of active development.