m1n64/lru-cache

Tests, release notes, a clear MIT license, and a small dependency set support basic transparency. The single-user project has little adoption and no security policy, so future maintenance remains uncertain.

Latest 1.1.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only two releases, both published within about two minutes on October 28, 2024, and none in the following nearly two years. This is strong evidence of stalled maintenance for a dependency.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with the long release gap and increasing abandonment risk.

Maintainers

Only one registry account has publish access. The repository is also owned by a single user, so there is no demonstrated organizational or contributor redundancy to compensate for that narrow base.

Repo popularity

The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these counts provide little external evidence of maturity or community support.

Repo tooling

Composer is used for the build, but no security scanning tools are configured. For a small package this is a hygiene gap rather than a severe defect.