Recordsgolanggolang.org/x/net
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
No recorded evidence matches these filters. Nothing is inferred; clear a filter to widen the slice.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.24.0
linux · go@1.26
5 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:d5fae02e8604b6955b8f1c65a8d5cc795aaceed9651a9f67da2c34536a6764a1
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/crypto | v0.22.0 | CANDIDATE Correlated change; unproven combination | contract passed | 28 project-days |
| golang.org/x/sys | v0.19.0 | CANDIDATE Correlated change; unproven combination | contract passed | 27 project-days |
| golang.org/x/term | v0.19.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 27 project-days |
| golang.org/x/text | v0.14.0 | CANDIDATE Correlated change; unproven combination | contract passed | 28 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.
Moved: 4 · 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.