CodeSampleX

Recordsnpmcacache16.1.3

Change the conditions
Fixed
Runtimenode 24 Package version16.1.3
Filter OSwindows 11 Symbolwhole package Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

cacache @16.1.3windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

0 of 11 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
25 / 28
Contract verifications
0 / 11
Usage records
46
Independent reporting peers
1
Failures with a captured fingerprint
1 / 3
Last recorded
2026-09-16
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 11 · Steady 7

First observed break

16.1.3

linux · node@22.23 · executionContext=node · moduleSystem=cjs

12 FAIL · stage: UNKNOWN · fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868

View exact conditions View failure cluster
Library Version Health Measured there Projects
@npmcli/fs 2.1.2 CANDIDATE Correlated change; unproven combination contract passed 18 project-days
fs-minipass 2.1.0 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
glob 8.1.0 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
lru-cache 7.18.3 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
minipass 3.3.6 CANDIDATE Correlated change; unproven combination contract passed 18 project-days
minipass-collect 1.0.2 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
minipass-flush 1.0.7 CANDIDATE Correlated change; unproven combination contract passed 16 project-days
p-map 4.0.0 CANDIDATE Correlated change; unproven combination contract passed 16 project-days
ssri 9.0.1 CANDIDATE Correlated change; unproven combination contract passed 16 project-days
tar 6.2.1 CANDIDATE Correlated change; unproven combination contract passed 18 project-days
unique-filename 2.0.1 CANDIDATE Correlated change; unproven combination contract passed 15 project-days
@npmcli/move-file 2.0.1 PASS All observations passed contract passed 18 project-days
chownr 2.0.0 PASS All observations passed contract passed 17 project-days
infer-owner 1.0.4 PASS All observations passed contract passed 17 project-days
minipass-pipeline 1.2.4 PASS All observations passed contract passed 17 project-days
mkdirp 1.0.4 PASS All observations passed contract passed 18 project-days
promise-inflight 1.0.1 PASS All observations passed contract passed 16 project-days
rimraf 3.0.2 PASS All observations passed contract passed 18 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.

Library20.0.420.0.319.0.116.1.3
@npmcli/fs 5.0.0 5.0.0 4.0.0 2.1.2
fs-minipass 3.0.3 3.0.3 3.0.3 2.1.0
glob 13.0.6 13.0.0 10.5.0 8.1.0
lru-cache 11.5.1 11.2.4 10.4.3 7.18.3
minipass 7.1.3 7.1.2 7.1.3 3.3.6
minipass-collect 2.0.1 2.0.1 2.0.1 1.0.2
minipass-flush 1.0.6 1.0.5 1.0.5 1.0.7
p-map 7.0.4 7.0.4 7.0.4 4.0.0
ssri 13.0.1 13.0.0 12.0.0 9.0.1
tar — — 7.5.22 6.2.1
unique-filename — 5.0.0 4.0.0 2.0.1
@npmcli/move-file — — — 2.0.1
chownr — — — 2.0.0
infer-owner — — — 1.0.4
minipass-pipeline 1.2.4 1.2.4 1.2.4 1.2.4
mkdirp — — — 1.0.4
promise-inflight — — — 1.0.1
rimraf — — — 3.0.2

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.

Recent failure clusters