CodeSampleX

Recordsgolanggithub.com/klauspost/cpuid/v2v2.2.10

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

Current conditions

github.com/klauspost/cpuid/v2 @v2.2.10ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 15 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
8 / 8
Contract verifications
0 / 15
Usage records
36
Independent reporting peers
2
Last recorded
2026-08-31
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

v2.2.10

go@1.26

4 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
golang.org/x/sys v0.30.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
golang.org/x/sys v0.31.0 CANDIDATE Correlated change; unproven combination contract passed 2 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.

Libraryv2.3.0v2.2.10
golang.org/x/sys v0.45.0 v0.31.0

Moved: 1 · unchanged at every release: 0

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