CodeSampleX

Recordsnpmfile-entry-cache8.0.0file-entry-cache.createFromFile

Change the conditions
Fixed
Symbolfile-entry-cache.createFromFile Package managernpm
Filter OSdebian glibc Runtimenode 22 Package version8.0.0 Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

file-entry-cache.createFromFile @8.0.0debian glibc · x64 · node 22 · npm · node

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
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-17

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

8.0.0

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

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

Library Version Health Measured there Projects
flat-cache 4.0.1 CANDIDATE Correlated change; unproven combination contract passed 23 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.

Library11.1.58.0.06.0.1
flat-cache 6.1.23 4.0.1 3.2.0

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.

Recent failure clusters