CodeSampleX

Recordsnpmmake-fetch-happen14.0.3fetch.defaults

Change the conditions
Fixed
Symbolfetch.defaults
Filter OSdebian glibc Runtimenode 22 Package version14.0.3 Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

fetch.defaults @14.0.3debian 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 (2)

Project observations
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-10-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 10 · Steady 4

First observed break

14.0.3

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

2 FAIL · stage: UNKNOWN · fingerprint: sha256:536db39a2e089f7ed603954e4a67695a077090ed80e3d0d1ef21bd2d6a9e9b21

View exact conditions View failure cluster
Library Version Health Measured there Projects
@npmcli/agent 3.0.0 CANDIDATE Correlated change; unproven combination contract passed 52 project-days
cacache 19.0.1 CANDIDATE Correlated change; unproven combination contract passed 52 project-days
minipass 7.1.3 CANDIDATE Correlated change; unproven combination contract passed 52 project-days
minipass-fetch 4.0.1 CANDIDATE Correlated change; unproven combination contract passed 50 project-days
minipass-flush 1.0.5 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
minipass-flush 1.0.7 CANDIDATE Correlated change; unproven combination contract passed 49 project-days
negotiator 1.0.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
negotiator 1.1.0 CANDIDATE Correlated change; unproven combination contract passed 49 project-days
proc-log 5.0.0 CANDIDATE Correlated change; unproven combination contract passed 52 project-days
ssri 12.0.0 CANDIDATE Correlated change; unproven combination contract passed 52 project-days
http-cache-semantics 4.2.0 PASS All observations passed contract passed 3 project-days
http-cache-semantics 4.3.0 PASS All observations passed contract passed 49 project-days
minipass-pipeline 1.2.4 PASS All observations passed contract passed 52 project-days
promise-retry 2.0.1 PASS All observations passed contract passed 52 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