Recordsgolanggolang.org/x/mod
Change the conditions
Current conditions
golang.org/x/mod @v0.6.0-dev.0.20220419223038-86c51ed26bb4ubuntu glibc · x64 · go 1.26 · go 1
0 of 4 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (1)
- Project observations
- 12 / 14
- Contract verifications
- 0 / 4
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-14
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 4 passed
Verified — this network ran a contract at this coordinate.
-
golang.org/x/mod/modfile.Parse
0 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
v0.6.0-dev.0.20220419223038-86c51ed26bb4
linux · go@1.26
2 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:964ddac6b19a356d0ae3f5727559d1fc36ac1222ed1964d18326e8a89565fde3
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/crypto | v0.0.0-20210921155107-089bfa567519 | CANDIDATE Correlated change; unproven combination | builds observed | 3 project-days |
| golang.org/x/crypto | v0.3.0 | CANDIDATE Correlated change; unproven combination | builds observed | 3 project-days |
| golang.org/x/tools | v0.1.12 | CANDIDATE Correlated change; unproven combination | contract passed | 7 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 | v0.39.0 | v0.38.0 | v0.37.0 | v0.35.0 | v0.33.0 | v0.24.0 | v0.18.0 | v0.13.0 | v0.8.0 | v0.6.0-dev.0.20220419223038-86c51ed26bb4 | v0.4.2 | v0.3.0 | v0.2.0 | v0.1.1-0.20191105210325-c90efee705ee | v0.0.0-20190513183733-4bf6d317e70e |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| golang.org/x/crypto | — | — | — | — | — | — | — | — | — | v0.3.0 | v0.0.0-20191011191535-87dc89f01550 | v0.0.0-20191011191535-87dc89f01550 | v0.0.0-20191011191535-87dc89f01550 | v0.0.0-20210711020723-a769d52b0f97 | v0.0.0-20190510104115-cbcb75029529 |
| golang.org/x/tools | v0.49.0 | v0.48.0 | v0.46.0 | v0.44.0 | v0.42.0 | v0.31.0 | v0.22.0 | v0.14.0 | v0.1.12 | v0.1.12 | v0.1.1 | v0.0.0-20200825202427-b303f430e36d | v0.0.0-20200331025713-a30bf2db82d4 | — | — |
| golang.org/x/xerrors | — | — | — | — | — | — | — | — | — | — | v0.0.0-20200804184101-5ec99f83aff1 | v0.0.0-20200804184101-5ec99f83aff1 | v0.0.0-20191204190536-9bdfabe68543 | v0.0.0-20200804184101-5ec99f83aff1 | — |
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.