packaged/cache

Its small dependency surface, tests, clear license, and matching organization-backed repository reduce adoption friction. The package remains operationally documented, but maintenance capacity is the main concern.

Latest 1.0.0

Packagist

35%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only 2 releases, and its latest release was nearly 10 years ago; there have been no releases in the last 12 months. This is strong evidence of abandonment risk.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the long release gap and offering no evidence of current maintenance.

Repo issue activity

There are 3 open issues, with no new or closed issues and no pull-request activity in the last month. This suggests unresolved maintenance needs.

Repo popularity

The repository has only 2 stars, 0 forks, and 3 watchers. Popularity is supporting evidence rather than a verdict, but these very small figures provide little evidence of a sustained user or contributor community.

Repo tooling

Composer is used for builds, which fits the package ecosystem, but no security-scanning tooling is present. This is a modest transparency and maintenance gap rather than a severe risk.