CodeSampleX

Recordsnpmelectron-builder-squirrel-windows25.1.8

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

Current conditions

electron-builder-squirrel-windows @25.1.8windows 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 (1)

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 2

First observed break

25.1.8

windows · executionContext=node

5 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
app-builder-lib 25.1.8 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
builder-util 25.1.7 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
archiver 5.3.2 PASS All observations passed contract passed 17 project-days
fs-extra 10.1.0 PASS All observations passed contract passed 17 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: 2 · unchanged at every release: 3

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