Recordsnpm@cacheable/utils
Change the conditions
Current conditions
@cacheable/utils @2.5.0debian glibc · x64 · node 22 · npm · node
10 of 10 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 (10)
- Project observations
- 8 / 8
- Contract verifications
- 10 / 10
- Usage records
- 8
- Independent reporting peers
- 2
- Last recorded
- 2026-09-17
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
10 of 10 passed
Verified — this network ran a contract at this coordinate.
-
CacheTags
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
2.5.0
linux · node@22.23 · executionContext=node · moduleSystem=cjs
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:0ab3a7004d66a92c85914b849316be1df344d8cf5f6a68edd66909ad7c806d71
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| hashery | 1.5.1 | PASS All observations passed | contract passed | 64 project-days |
| keyv | 5.6.0 | PASS All observations passed | contract passed | 64 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.