getpop/cache-control

This is a healthy, actively maintained release with a strong release history, stable versioning, a current non-archived repository, clear licensing, tests, and a small dependency footprint. The main concern is concentrated maintenance: all 15 commits in the last 3 months came from one contributor, despite the repository being organization-owned, and the repository has no security scanning or security policy. Very low popularity is supporting caution but not decisive, while the absence of install-time lifecycle scripts and the presence of repository-backed tests reduce supply-chain and abandonment concerns.

Latest 19.2.4

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

One contributor made 100% of the 15 recent commits, creating a genuine continuity risk; organization ownership provides some handoff potential but no second active contributor is shown.

Repo commit activity

The repository recorded 15 commits in the last 3 months, showing active development, but all were made by one active maintainer.

Repo popularity

The repository has only 1 star, 0 forks, and 1 watcher, which limits external validation and community depth; however, popularity is supporting evidence and the package demonstrates substantial release activity.

Repo tooling

Composer is used as a build tool, but no security scanning tools are configured. The missing scanning reduces defense-in-depth, though it is not by itself evidence of poor maintenance.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations less transparent for dependents.