CodeSampleX

Recordsnpmmake-fetch-happen10.2.1

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

Current conditions

make-fetch-happen @10.2.1windows 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 6 · Steady 10

First observed break

10.2.1

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

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
cacache 16.1.3 CANDIDATE Correlated change; unproven combination contract passed 19 project-days
minipass 3.3.6 CANDIDATE Correlated change; unproven combination contract passed 19 project-days
minipass-fetch 2.1.2 CANDIDATE Correlated change; unproven combination contract passed 18 project-days
minipass-flush 1.0.7 CANDIDATE Correlated change; unproven combination contract passed 19 project-days
negotiator 0.6.4 CANDIDATE Correlated change; unproven combination contract passed 18 project-days
ssri 9.0.1 CANDIDATE Correlated change; unproven combination contract passed 19 project-days
agentkeepalive 4.6.0 PASS All observations passed contract passed 19 project-days
http-cache-semantics 4.2.0 PASS All observations passed contract passed 19 project-days
http-proxy-agent 5.0.0 PASS All observations passed contract passed 19 project-days
https-proxy-agent 5.0.1 PASS All observations passed contract passed 19 project-days
is-lambda 1.0.1 PASS All observations passed contract passed 19 project-days
lru-cache 7.18.3 PASS All observations passed contract passed 19 project-days
minipass-collect 1.0.2 PASS All observations passed contract passed 19 project-days
minipass-pipeline 1.2.4 PASS All observations passed contract passed 19 project-days
promise-retry 2.0.1 PASS All observations passed contract passed 19 project-days
socks-proxy-agent 7.0.0 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.

Library15.0.615.0.314.0.310.2.1
@npmcli/agent 4.0.2 4.0.0 3.0.0 —
cacache 20.0.4 20.0.3 19.0.1 16.1.3
minipass 7.1.3 7.1.2 7.1.3 3.3.6
minipass-fetch 5.0.2 5.0.0 4.0.1 2.1.2
minipass-flush 1.0.6 1.0.5 1.0.5 1.0.7
negotiator 1.0.0 1.0.0 1.0.0 0.6.4
proc-log 6.1.0 6.1.0 5.0.0 —
ssri 13.0.1 13.0.0 12.0.0 9.0.1
@gar/promise-retry 1.0.3 — — —
@npmcli/redact 4.0.0 — — —
agentkeepalive — — — 4.6.0
http-cache-semantics 4.2.0 4.2.0 4.2.0 4.2.0
http-proxy-agent — — — 5.0.0
https-proxy-agent — — — 5.0.1
is-lambda — — — 1.0.1
lru-cache — — — 7.18.3
minipass-collect — — — 1.0.2
minipass-pipeline 1.2.4 1.2.4 1.2.4 1.2.4
promise-retry — 2.0.1 2.0.1 2.0.1
socks-proxy-agent — — — 7.0.0

Moved: 8 · unchanged at every release: 12

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