phlib/config-pool

Clear documentation, a focused dependency footprint, and repository tests make the package straightforward to evaluate. Maintenance has been quiet since the sole release, and the workflow uses four unpinned actions. The organization-backed repository is intact and the package is properly licensed.

Latest 1.0.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the package's only release, published about 22 months ago, with no releases in the last 12 months. That limited history and long inactivity reduce confidence in ongoing maintenance.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Combined with the single historical release, this is meaningful evidence of currently quiet maintenance.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.

Security policy

The repository has no security policy. For a small library this is a transparency gap, although it is less significant than evidence of abandonment.

Workflow audit

The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, all four action references are unpinned, leaving avoidable supply-chain hygiene risk.