CodeSampleX

Recordsnpmlru-cache5.1.1

Change the conditions
Fixed
OSalpine musl Package version5.1.1 Package managernpm
Filter Runtimenode 22 Symbolwhole package Architecturex64 Execution contextnode libcmusl Clear filters

Current conditions

lru-cache @5.1.1alpine musl · x64 · node 22 · npm · node

package-level total, not an API

2 of 2 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (2)

Project observations
4 / 4
Contract verifications
2 / 2
Usage records
2
Independent reporting peers
1
Last recorded
2026-08-30

Dependencies

LibraryVersionMeasured thereProjects
yallist 3.1.1 contract passed 27 project-days

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Library6.0.05.1.1
yallist 4.0.0 3.1.1

Moved: 1 · unchanged at every release: 0

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.

Recent failure clusters