entere/utils

The project is very small, has no tests or security policy, and provides only brief documentation. Its MIT license, matching repository, and lack of install scripts reduce adoption friction, but maintenance evidence is too old for a dependable current dependency.

Latest v0.1

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published about 8 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.

Repo commit activity

There were no commits or active maintainers in the last three months. Combined with the repository's last push in 2018, this materially raises maintenance and abandonment risk.

Repo tooling

Composer is used as the build tool, but no security scanning tooling is present. This is a modest transparency and maintenance gap rather than a standalone dependency blocker.

Security policy

The repository has no security policy. For a small, inactive package this leaves vulnerability-reporting expectations unclear and adds to its transparency concerns.

Version stability

The only version is v0.1, so the package has little demonstrated release maturity. Its non-prerelease status provides only limited reassurance because there is no subsequent release history.