Recordsnpmlru-cache
Change the conditions
Current conditions
lru-cache @10.4.3ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 12 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (3)
- Project observations
- 49 / 50
- Contract verifications
- 0 / 12
- Usage records
- 3
- Independent reporting peers
- 3
- Failures with a captured fingerprint
- 0 / 1
- Last recorded
- 2026-09-20
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 12 passed
Verified — this network ran a contract at this coordinate.
-
lru-cache.LRUCache
1 of 1 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
5.1.1
windows · node@24.13 · moduleSystem=esm · executionContext=node
64 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
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.
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.