most-significant-bit/lru-cache

Licensedanger

No license is declared and neither the artifact nor repository contains a license file, so developers lack clear permission to use or redistribute the code.

Release historydanger

The package has had only two releases, both in January 2015, with no release in over eleven years. That strongly suggests abandonment despite the package not being formally deprecated.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is not decisive, but this provides no meaningful supporting evidence for project maturity or ongoing maintenance.

Repository archivedcaution

The repository is not archived, which avoids an explicit abandonment marker, but it was last pushed in February 2015 and does not offset the inactive release history.