CodeSampleX

Recordsnpmelectron38.8.6

Change the conditions
Fixed
OSubuntu glibc Package version38.8.6 Execution contextnode
Filter Runtimenode 22 Symbolwhole package Architecturex64 Package managernpm 10 libcglibc Clear filters

Current conditions

electron @38.8.6ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 50 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (20)

Project observations
29 / 33
Contract verifications
0 / 50
Usage records
91
Independent reporting peers
3
Failures with a captured fingerprint
0 / 4
Last recorded
2026-09-06
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 1

First observed break

38.8.6

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

47 FAIL · stage: UNKNOWN · fingerprint: sha256:979755e6489d54fbc02ff712a1ad44c541d0fea0a79afc307d5bbd18aef3107a

View exact conditions View failure cluster
Library Version Health Measured there Projects
@electron/get 2.0.3 CANDIDATE Correlated change; unproven combination contract passed 10 project-days
@types/node 22.20.1 CANDIDATE Correlated change; unproven combination contract passed 10 project-days
extract-zip 2.0.1 PASS All observations passed contract passed 10 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.

Library43.4.143.2.038.8.638.0.033.4.11
@electron/get 5.1.0 5.1.0 2.0.3 2.0.3 2.0.3
@types/node 24.13.3 24.13.3 22.20.1 22.20.1 20.19.43
@electron-internal/extract-zip 1.0.5 1.0.5 — — —
extract-zip — — 2.0.1 2.0.1 2.0.1

Moved: 2 · unchanged at every release: 2

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