CodeSampleX

Recordsnpmflat-cache4.0.1

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

Current conditions

flat-cache @4.0.1alpine musl · x64 · node 22 · npm · node

package-level total, not an API

2 of 2 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 (2)

Project observations
4 / 4
Contract verifications
2 / 2
Usage records
2
Independent reporting peers
1
Last recorded
2026-08-30
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 1

First observed break

4.0.1

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

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
flatted 3.4.3 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
flatted 3.4.4 CANDIDATE Correlated change; unproven combination contract passed 23 project-days
keyv 4.5.4 PASS All observations passed contract passed 27 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.

Library6.1.234.0.13.2.0
flatted 3.4.4 3.4.3 3.3.3
cacheable 2.5.0 — —
hookified 1.15.1 — —
keyv — 4.5.4 4.5.4
rimraf — — 3.0.2

Moved: 1 · unchanged at every release: 4

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