zhengguoze/mycache2

Risky to adopt: this package has had no release or repository activity since September 2021, with only two releases and no users or forks. It is small and understandable, with a matching repository, tests, a README, and an MIT declaration, but its long inactivity makes maintenance uncertain.

Latest 1.0.1

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is about five years old but has only two releases, both clustered on its first day, and none in the last 12 months. This strongly indicates abandonment risk despite the stable 1.0.1 version.

Maintainers

A single registry maintainer is consistent with a user-owned small project, but it provides little redundancy if that person stops maintaining it. The repository's matching ownership confirms accountability but not active maintenance.

Repo popularity

The repository has zero stars and forks and only one watcher, offering no supporting evidence of community review or shared maintenance. Low popularity alone is not disqualifying, but it reinforces the inactivity concern.

Repo tooling

Composer build tooling is present, but no security scanning tooling was found. For this small package this is a transparency gap rather than a severe risk, and the absence of workflows limits the practical significance.

Repository archived

The repository is not formally archived, which avoids the most severe abandonment signal, but its last push was about five years ago and does not offset the stale release history.