CodeSampleX

Recordsnpmelectron-publish25.1.7HttpPublisher

Change the conditions
Fixed
SymbolHttpPublisher Package managernpm
Filter OSdebian glibc Runtimenode 22 Package version25.1.7 Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

HttpPublisher @25.1.7debian 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 (1)

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 5

First observed break

25.1.7

moduleSystem=cjs · executionContext=node

6 FAIL · stage: UNKNOWN · fingerprint: sha256:bc4d7ddc5bcdb4d412bf4a8bb2673c786c7e3852044dc88acdc3e1dc4e6f49cb

View exact conditions View failure cluster
Library Version Health Measured there Projects
builder-util 25.1.7 CANDIDATE Correlated change; unproven combination contract passed 23 project-days
builder-util-runtime 9.2.10 CANDIDATE Correlated change; unproven combination contract passed 23 project-days
@types/fs-extra 9.0.13 PASS All observations passed contract passed 23 project-days
chalk 4.1.2 PASS All observations passed contract passed 23 project-days
fs-extra 10.1.0 PASS All observations passed contract passed 23 project-days
lazy-val 1.0.5 PASS All observations passed contract passed 23 project-days
mime 2.6.0 PASS All observations passed contract passed 22 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.

Library26.15.325.1.7
builder-util 26.15.3 25.1.7
builder-util-runtime 9.7.0 9.2.10
@types/fs-extra 9.0.13 9.0.13
aws4 1.13.2 —
chalk 4.1.2 4.1.2
form-data 4.0.6 —
fs-extra 10.1.0 10.1.0
lazy-val 1.0.5 1.0.5
mime 2.6.0 2.6.0

Moved: 2 · 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