CodeSampleX

Recordsnpmmake-fetch-happen15.0.6

Change the conditions
Fixed
OSubuntu glibc Package version15.0.6 Package managernpm 10
Filter Runtimenode 22 Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

make-fetch-happen @15.0.6ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 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 failed

Project observations
1 / 1
Contract verifications
0 / 1
Independent reporting peers
1
Last recorded
2026-09-14

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 8 · Steady 4

First observed break

15.0.6

linux · node@22.23 · executionContext=node

3 FAIL · stage: UNKNOWN · fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc

Library Version Health Measured there Projects
@npmcli/agent 4.0.2 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
cacache 20.0.4 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
minipass 7.1.3 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
minipass-fetch 5.0.2 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
minipass-flush 1.0.6 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
negotiator 1.0.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
proc-log 6.1.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
ssri 13.0.1 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
@gar/promise-retry 1.0.3 PASS All observations passed contract passed 2 project-days
@npmcli/redact 4.0.0 PASS All observations passed contract passed 2 project-days
http-cache-semantics 4.2.0 PASS All observations passed contract passed 2 project-days
minipass-pipeline 1.2.4 PASS All observations passed contract passed 2 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.

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