Recordsnpmlru-cache
Change the conditions
Current conditions
lru-cache @6.0.0alpine musl · x64 · node 22 · npm · node
3 of 3 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 (3)
- Project observations
- 4 / 4
- Contract verifications
- 3 / 3
- Usage records
- 2
- Independent reporting peers
- 1
- Last recorded
- 2026-08-30
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
LRU.set
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
3 of 3 passed
Verified — this network ran a contract at this coordinate.
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| yallist | 4.0.0 | contract passed | 6 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.
| Library | 6.0.0 | 5.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.