Records npmelectron-updater

Change the conditions

Current conditions

AppUpdater @6.8.9x64 · node 22 · node

1 of 12 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and this coordinate records both a passing and a failing run of it (1)

Project observations: 10 / 10
Contract verifications: 1 / 12
Independent reporting peers: 3
Last recorded: 2026-08-30

Evidence you can open

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

alpine musl · x64 · node 22 · npm · node

1 of 1 passed

Open the next level

Verified — this network ran a contract at this coordinate.
ubuntu glibc · x64 · node 22 · npm 10 · node

0 of 11 passed

Open the next level

Verified — this network ran a contract at this coordinate.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 6

First observed break

6.8.9

windows · node@24.13 · moduleSystem=esm · executionContext=node

32 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

View exact conditions View failure cluster

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.

Library	6.8.9	6.3.9
builder-util-runtime	9.7.0	9.2.10
semver	7.7.4	7.8.5
fs-extra	10.1.0	10.1.0
js-yaml	4.3.2	4.3.2
lazy-val	1.0.5	1.0.5
lodash.escaperegexp	4.1.2	4.1.2
lodash.isequal	4.5.0	4.5.0
tiny-typed-emitter	2.1.0	2.1.0

Moved: 2 · unchanged at every release: 6

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.