mintyphp/core

Healthy and actively usable, with strong release history, clear licensing, tests, and a matching organization-backed repository. The main caveat is that recent work is limited to two commits from one contributor, with no security policy or automated security scanning.

Latest v4.0.7

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access, which is a resilience concern, although the repository is owned by an organization and the long release history shows the account has been active.

Repo bus factor

All recent commits came from one contributor, creating concentration risk. Organization ownership partly compensates because maintenance can potentially be handed off internally.

Repo commit activity

The repository recorded two commits in the last 3 months from one active maintainer. Work is continuing, but the low volume limits evidence of strong ongoing maintenance.

Repo issue activity

There are no open issues or pull requests, and no recent issue or pull-request activity. This is not a problem by itself, but it provides little evidence of a broader support community.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured, leaving a security-hygiene gap in the repository.