Package Health/api-clients/test-utilities

api-clients/test-utilities

Usable with caveats: the package is clearly backed by a matching organization repository, has tests, a readable README, licensing, and modern build and security tooling. However, it has had no registry releases in nearly five years and no commits in the last three months, so future maintenance is uncertain.

Latest 5.5.0

Packagist

62%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Lifecycle scripts

The package defines post-install and post-update Composer scripts, meaning dependency installation can execute package-provided actions. This deserves review by consumers, although the available workflow analysis shows no dangerous repository automation patterns.

Release history

The latest recorded release was nearly five years ago, and there were no releases in the last 12 months. That is a meaningful maintenance concern for a dependency, despite the package having 19 releases over its lifetime.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, indicating currently inactive development. The repository is not archived, but that does not demonstrate active maintenance.

Security policy

No repository security policy was found, leaving vulnerability-reporting guidance undocumented. This is a transparency gap, but it is not by itself evidence that the package is unsafe.

Token permissions

All four workflows lack top-level token-permission declarations, so their intended GitHub token scope is less explicit than best practice. No workflow declares top-level write access, which limits the severity of this gap.