CodeSampleX

Recordsnpm@electron/get5.1.0

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

Current conditions

@electron/get @5.1.0ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 12 passed

Verified — this network ran a contract at this coordinate.

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

Project observations
25 / 25
Contract verifications
0 / 12
Usage records
29
Independent reporting peers
2
Last recorded
2026-08-31

Dependencies

LibraryVersionMeasured thereProjects
debug 4.4.3 contract passed 3 project-days
env-paths 3.0.0 contract passed 3 project-days
graceful-fs 4.2.11 contract passed 3 project-days
progress 2.0.3 contract passed 3 project-days
semver 7.7.4 contract passed 1 project-day
semver 7.8.5 contract passed 2 project-days
sumchecker 3.0.1 contract passed 3 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