kgolinski/turboenum

The package has a clear MIT license, tests in the repository, and minimal runtime dependencies. Its single release, no commits in the last three months, missing security policy, and workflow permission and pinning issues make long-term maintenance less certain.

Latest 1.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Lifecycle scripts

A post-autoload-dump install script adds execution during installation, creating some supply-chain exposure, though this is a limited and common Composer lifecycle hook rather than evidence of an unsafe package.

Project backing

The package and repository are owned by the same individual account, so the source relationship is clear, but there is no organization backing to compensate for a single-owner project.

Release history

This is the only release since the package launched about 10 months ago, so there is little release history from which to judge maturity or ongoing maintenance.

Repo commit activity

No commits and no active maintainers were recorded during the last three months, which weakens evidence of current maintenance for a package with only one release.

Security policy

The repository has no security policy, leaving contributors and users without a documented reporting path; this is a transparency gap for a package intended for dependency use.