mezon/conf

The package includes tests, documentation, and a permissive license, with no install scripts or deprecation notice. Its single-maintainer footprint and absent security tooling leave long-term support uncertain.

Latest 1.2.3

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. For a user-owned project this suggests a thin support base and limited continuity if that maintainer becomes inactive.

Release history

The package has 15 releases and a median interval of about 22 days, but it has had no release in more than three years. That long pause materially raises abandonment risk.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the long release pause. This is a meaningful maintenance concern even though the repository is not archived.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence of an unsafe release.

Security policy

The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a hygiene gap, but it is partly offset by the package's small scope and test coverage.