Recordsgolanggolang.org/x/modv0.39.0
Change the conditions
Current conditions
golang.org/x/mod @v0.39.0debian glibc · x64 · go 1.26 · go · go
package-level total, not an API
13 of 13 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (13)
- Project observations
- 18 / 18
- Contract verifications
- 13 / 13
- Usage records
- 10
- Independent reporting peers
- 1
- Last recorded
- 2026-10-13
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.39.0
linux · go@1.26
2 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:964ddac6b19a356d0ae3f5727559d1fc36ac1222ed1964d18326e8a89565fde3
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/tools | v0.48.0 | CANDIDATE Correlated change; unproven combination | contract passed | 13 project-days |
| golang.org/x/tools | v0.49.0 | CANDIDATE Correlated change; unproven combination | 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.
Moved: 3 · 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
-
observed PROJECT_COMPILE exit 1 ×2 v0.6.0-dev.0.20220419223038-86c51ed26bb4 → v0.39.0 os=linux · runtime=go@1.26 sha256:964ddac6b19a…<path> <str> imported and not usedgo/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-06 · Last seen: 2026-10-09