CodeSampleX

Recordsnpmapp-builder-lib25.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

app-builder-lib @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 (9)

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 10 · Steady 23

First observed break

25.1.8

windows · executionContext=node

5 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
@electron/osx-sign 1.3.1 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
@electron/rebuild 3.6.1 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
@electron/universal 2.0.1 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
builder-util 25.1.7 CANDIDATE Correlated change; unproven combination contract passed 16 project-days
builder-util-runtime 9.2.10 CANDIDATE Correlated change; unproven combination contract passed 16 project-days
electron-publish 25.1.7 CANDIDATE Correlated change; unproven combination contract passed 15 project-days
js-yaml 4.3.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
js-yaml 4.3.2 CANDIDATE Correlated change; unproven combination contract passed 12 project-days
semver 7.8.5 CANDIDATE Correlated change; unproven combination contract passed 16 project-days
tar 6.2.1 CANDIDATE Correlated change; unproven combination contract passed 16 project-days
@develar/schema-utils 2.6.5 PASS All observations passed contract passed 17 project-days
@electron/notarize 2.5.0 PASS All observations passed contract passed 17 project-days
@malept/flatpak-bundler 0.4.0 PASS All observations passed contract passed 17 project-days
@types/fs-extra 9.0.13 PASS All observations passed contract passed 16 project-days
async-exit-hook 2.0.1 PASS All observations passed contract passed 17 project-days
bluebird-lst 1.0.9 PASS All observations passed contract passed 16 project-days
chromium-pickle-js 0.2.0 PASS All observations passed contract passed 16 project-days
config-file-ts 0.2.8-rc1 PASS All observations passed contract passed 16 project-days
debug 4.4.3 PASS All observations passed contract passed 17 project-days
dotenv 16.6.1 PASS All observations passed contract passed 15 project-days
dotenv-expand 11.0.7 PASS All observations passed contract passed 15 project-days
ejs 3.1.10 PASS All observations passed contract passed 15 project-days
form-data 4.0.6 PASS All observations passed contract passed 14 project-days
fs-extra 10.1.0 PASS All observations passed contract passed 15 project-days
hosted-git-info 4.1.0 PASS All observations passed contract passed 13 project-days
is-ci 3.0.1 PASS All observations passed contract passed 13 project-days
isbinaryfile 5.0.7 PASS All observations passed contract passed 13 project-days
json5 2.2.3 PASS All observations passed contract passed 14 project-days
lazy-val 1.0.5 PASS All observations passed contract passed 13 project-days
minimatch 10.2.6 PASS All observations passed contract passed 15 project-days
resedit 1.7.2 PASS All observations passed contract passed 14 project-days
sanitize-filename 1.6.4 PASS All observations passed contract passed 13 project-days
temp-file 3.4.0 PASS All observations passed contract passed 14 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.8
@electron/osx-sign 1.3.3 1.3.1
@electron/rebuild 4.2.0 3.6.1
@electron/universal 2.0.3 2.0.1
builder-util 26.15.3 25.1.7
builder-util-runtime 9.7.0 9.2.10
electron-publish 26.15.3 25.1.7
js-yaml 4.3.2 4.3.0
semver 7.7.4 7.8.5
tar 7.5.22 6.2.1
@develar/schema-utils — 2.6.5
@electron/asar 3.4.1 —
@electron/fuses 1.8.0 —
@electron/get 3.1.0 —
@electron/notarize 2.5.0 2.5.0
@malept/flatpak-bundler 0.4.0 0.4.0
@noble/hashes 2.3.0 —
@peculiar/webcrypto 1.7.1 —
@types/fs-extra 9.0.13 9.0.13
ajv 8.20.0 —
asn1js 3.0.10 —
async-exit-hook 2.0.1 2.0.1
bluebird-lst — 1.0.9
chromium-pickle-js 0.2.0 0.2.0
ci-info 4.3.1 —
config-file-ts — 0.2.8-rc1
debug 4.4.3 4.4.3
dotenv 16.6.1 16.6.1
dotenv-expand 11.0.7 11.0.7
ejs 3.1.10 3.1.10
form-data — 4.0.6
fs-extra 10.1.0 10.1.0
hosted-git-info 4.1.0 4.1.0
is-ci — 3.0.1
isbinaryfile 5.0.7 5.0.7
jiti 2.7.0 —
json5 2.2.3 2.2.3
lazy-val 1.0.5 1.0.5
minimatch 10.2.6 10.2.6
pkijs 3.4.0 —
plist 3.1.0 —

Moved: 9 · unchanged at every release: 38 Longer lists are cut here; the counts above cover all of them.

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