CodeSampleX

Recordsnpmlru-cache6.0.0LRU.set

Change the conditions
Fixed
Package version6.0.0 SymbolLRU.set
Filter OSalpine musl Runtimenode 22 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

LRU.set @6.0.0alpine musl · x64 · node 22 · npm · node

1 of 1 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 (1)

Project observations
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-20
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

6.0.0

windows · node@24.13 · executionContext=node · moduleSystem=esm

62 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

View exact conditions View failure cluster
Library Version Health Measured there Projects
yallist 4.0.0 CANDIDATE Correlated change; unproven combination 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