slava-basko/enum

It includes tests, a clear BSD-2-Clause license, a useful README, and no runtime dependencies. The lack of security scanning and a single maintainer leaves limited ongoing oversight.

Latest 1.0.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

One registry account has publish access. For this user-owned project that is consistent with individual ownership, but it leaves a thin maintainer base if the author becomes unavailable.

Project backing

The repository is owned by the same individual namespace as the package, with no organization backing shown. This is coherent ownership evidence but offers limited redundancy.

Release history

The package has had only one release, published about four years ago, with no releases in the last 12 months. This strongly limits evidence of active maintenance, although a stable legacy library can remain serviceable without frequent releases.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old last push, this indicates little current maintenance capacity.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tool was detected. The missing scanner is a modest transparency and oversight gap.