Recordsnpmkeyv
Change the conditions
Current conditions
keyv @5.6.0ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 7 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed
- Project observations
- 74 / 75
- Contract verifications
- 0 / 7
- Usage records
- 3
- Independent reporting peers
- 3
- Last recorded
- 2026-09-06
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 7 passed
Verified — this network ran a contract at this coordinate.
-
keyv.Keyv
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.6.0
linux · node@22.23 · moduleSystem=cjs · executionContext=node
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:88af852f99a8104e4bc3c23eea27ebf2990625ccabf45313970f5fd7fe56c4e2
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @keyv/serialize | 1.1.1 | 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.
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 | 5.6.0 | 4.5.4 |
|---|---|---|
| @keyv/serialize | 1.1.1 | — |
| json-buffer | — | 3.0.1 |
Moved: 0 · unchanged at every release: 2
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.