CodeSampleX

Recordsnpm@electron/universal2.0.1

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

Current conditions

@electron/universal @2.0.1windows 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 (2)

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

First observed break

2.0.1

windows · executionContext=node

5 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
@electron/asar 3.4.1 PASS All observations passed contract passed 20 project-days
@malept/cross-spawn-promise 2.0.0 PASS All observations passed contract passed 20 project-days
debug 4.4.3 PASS All observations passed contract passed 20 project-days
dir-compare 4.2.0 PASS All observations passed contract passed 19 project-days
fs-extra 11.4.0 PASS All observations passed contract passed 19 project-days
minimatch 9.0.9 PASS All observations passed contract passed 18 project-days
plist 3.1.1 PASS All observations passed contract passed 19 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.

Library2.0.32.0.1
@electron/asar 3.4.1 3.4.1
@malept/cross-spawn-promise 2.0.0 2.0.0
debug 4.4.3 4.4.3
dir-compare 4.2.0 4.2.0
fs-extra 11.4.0 11.4.0
minimatch 9.0.9 9.0.9
plist 3.1.1 3.1.1

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