CodeSampleX

Recordsnpmcacache20.0.3

Change the conditions
Fixed
Runtimenode 22 Package version20.0.3
Filter OSdebian glibc Symbolwhole package Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

cacache @20.0.3debian glibc · x64 · node 22 · npm · node

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-14

Dependency Health

Observed combinations and failure evidence for this release

Changed 10 · Steady 1

Dependency changes observed: 10. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
@npmcli/fs 5.0.0 CHANGED Version changed, no linked failure contract passed 1 project-day
fs-minipass 3.0.3 CHANGED Version changed, no linked failure contract passed 1 project-day
glob 13.0.0 CHANGED Version changed, no linked failure builds observed 1 project-day
lru-cache 11.2.4 CHANGED Version changed, no linked failure contract passed 1 project-day
minipass 7.1.2 CHANGED Version changed, no linked failure contract passed 1 project-day
minipass-collect 2.0.1 CHANGED Version changed, no linked failure contract passed 1 project-day
minipass-flush 1.0.5 CHANGED Version changed, no linked failure contract passed 1 project-day
p-map 7.0.4 CHANGED Version changed, no linked failure contract passed 1 project-day
ssri 13.0.0 CHANGED Version changed, no linked failure builds observed 1 project-day
unique-filename 5.0.0 CHANGED Version changed, no linked failure builds observed 1 project-day
minipass-pipeline 1.2.4 PASS All observations passed contract passed 1 project-day

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.

Moved: 11 · unchanged at every release: 7

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.