CodeSampleX

Recordsnpmkeyv4.5.4

Change the conditions
Fixed
OSalpine musl Symbolwhole package
Filter Runtimenode 22 Package version4.5.4 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

keyv @4.5.4alpine musl · x64 · node 22 · npm · node

package-level total, not an API

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
2 / 2
Contract verifications
1 / 1
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-05

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 1

First observed break

4.5.4

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

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

Library Version Health Measured there Projects
json-buffer 3.0.1 PASS All observations passed contract passed 56 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.

Library5.6.04.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.

Recent failure clusters

Showing the 12 most-reported of 31 recorded failure clusters. The rest are single reports.