mindy/cache

The package includes tests, a stable major release, a declared BSD license, and no install-time scripts. Its very old activity and weak repository linkage make long-term maintenance and provenance concerns significant.

Latest 2.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in August 2016, with no releases in the last 12 months despite the package being over 11 years old. This is strong evidence of abandonment risk.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. Combined with the old last push, this supports an abandonment concern.

Repo package mention

The repository name does not match the package name and its README does not mention the package. This weakens confidence that the linked repository is the actual source, although a subpackage or monorepo can explain a name mismatch.

Repo popularity

The repository has zero stars, one fork, and one watcher. Popularity is supporting evidence rather than a verdict, but these figures provide little evidence of an active user community.

Repo tooling

Composer is used as the build tool, but no security scanning tooling is present. The missing scanning is a hygiene gap rather than evidence that the release is unsafe.