Recordsgolanggithub.com/klauspost/cpuid/v2
Change the conditions
Current conditions
cpuid.CPU @v2.2.10x64 · go 1.26 · go · go
1 of 2 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and this coordinate records both a passing and a failing run of it (1)
- Project observations
- 0 / 1
- Contract verifications
- 1 / 2
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 1
- Last recorded
- 2026-09-07
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
debian glibc · x64 · go 1.26 · go · go
0 of 1 passed
Verified — this network ran a contract at this coordinate.
-
alpine musl · x64 · go 1.26 · go · go
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
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.
| Library | v2.3.0 | v2.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.