CodeSampleX

Recordsgolanggithub.com/klauspost/cpuid/v2v2.2.10github.com/klauspost/cpuid/v2.CombineFeatures

Change the conditions
Fixed
Symbolgithub.com/klauspost/cpuid/v2.CombineFeatures
Filter OSubuntu glibc Runtimego 1.26 Package versionv2.2.10 Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

github.com/klauspost/cpuid/v2.CombineFeatures @v2.2.10ubuntu glibc · x64 · go 1.26 · go 1

2 of 2 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
2 / 2
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-26

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

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

Showing the 12 most-reported of 16 recorded failure clusters. The rest are single reports.