CodeSampleX

Recordsnpm@electron/get5.1.0

Change the conditions
Fixed
Runtimenode (version not recorded) Package version5.1.0
Filter OSwindows 11 Symbolwhole package Architecturex64 Package managernpm Execution contextnode Clear filters

Current conditions

@electron/get @5.1.0windows 11 · x64 · node (version not recorded) · npm · node

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-13
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Steady 3

First observed break

5.1.0

executionContext=node

10 FAIL · stage: PROCESS_START · fingerprint: sha256:c12549970456efb5abdc90b679695c6689107d4f097d612245d6bfb25e01ec32

View exact conditions View failure cluster
Library Version Health Measured there Projects
debug 4.4.3 CANDIDATE Correlated change; unproven combination contract passed 13 project-days
env-paths 3.0.0 CANDIDATE Correlated change; unproven combination contract passed 13 project-days
semver 7.7.4 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
semver 7.8.5 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
graceful-fs 4.2.11 PASS All observations passed contract passed 13 project-days
progress 2.0.3 PASS All observations passed contract passed 13 project-days
sumchecker 3.0.1 PASS All observations passed contract passed 13 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.

Library5.1.03.1.02.0.3
debug 4.4.3 4.4.3 4.3.7
env-paths 3.0.0 2.2.1 2.2.1
semver 7.7.4 6.3.1 6.3.1
fs-extra — 8.1.0 8.1.0
got — 11.8.6 11.8.6
graceful-fs 4.2.11 — —
progress 2.0.3 2.0.3 2.0.3
sumchecker 3.0.1 3.0.1 3.0.1

Moved: 3 · unchanged at every release: 5

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