Recordsgolanggolang.org/x/tools
Change the conditions
Current conditions
golang.org/x/tools @v0.44.0linux · glibc · x64 · node 22 · npm 10 · node
0 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (4)
- Project observations
- 15 / 15
- Contract verifications
- 0 / 1
- Independent reporting peers
- 2
- Last recorded
- 2026-09-04
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 1 passed
Verified — this network ran a contract at this coordinate.
-
golang.org/x/tools/go/types/typeutil.MethodSetCacheubuntu glibc · x64 · node 22 · npm 10 · node
1 of 1 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.44.0
linux
7 FAIL
· stage: UNKNOWN
· fingerprint: sha256:91ad26545eb1f3df29e3d9731c4244f3cf919942db2aa314b6b8d67ca84b47ef
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/google/go-cmp | v0.6.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 6 project-days |
| github.com/google/go-cmp | v0.7.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| github.com/yuin/goldmark | v1.4.13 | CANDIDATE Correlated change; unproven combination | nothing measured | 6 project-days |
| github.com/yuin/goldmark | v1.8.2 | CANDIDATE Correlated change; unproven combination | nothing measured | 1 project-day |
| golang.org/x/mod | v0.35.0 | CANDIDATE Correlated change; unproven combination | contract passed | 8 project-days |
| golang.org/x/net | v0.53.0 | CANDIDATE Correlated change; unproven combination | contract passed | 6 project-days |
| golang.org/x/net | v0.55.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| golang.org/x/sync | v0.20.0 | CANDIDATE Correlated change; unproven combination | contract passed | 8 project-days |
| golang.org/x/telemetry | v0.0.0-20260409153401-be6f6cb8b1fa | CANDIDATE Correlated change; unproven combination | nothing measured | 6 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: 8 · unchanged at every release: 2
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.