Recordsgolanggolang.org/x/toolsv0.22.0
Change the conditions
Current conditions
golang.org/x/tools @v0.22.0alpine musl · x64 · go 1.26 · go · go
package-level total, not an API
1 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 came back clean (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-30
Dependencies
Nothing has resolved this release yet, so its dependencies are unread rather than empty. See where it is counted
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.44.0 | v0.1.12 |
|---|---|---|
| github.com/yuin/goldmark | v1.8.2 | v1.4.13 |
| golang.org/x/mod | v0.35.0 | v0.6.0-dev.0.20220419223038-86c51ed26bb4 |
| golang.org/x/net | v0.53.0 | v0.4.0 |
| golang.org/x/sync | v0.20.0 | v0.21.0 |
| github.com/google/go-cmp | v0.6.0 | — |
| golang.org/x/sys | — | v0.47.0 |
| golang.org/x/telemetry | v0.0.0-20260409153401-be6f6cb8b1fa | — |
| golang.org/x/text | — | v0.5.0 |
Moved: 4 · unchanged at every release: 4
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 ×1 v0.22.0 os=linux · runtime=go@1.26 sha256:2a6c03dbb82c…test/contract.go:<n>:<n>: cannot use func(n ast.Node, push bool) bool {…} (value of type func(n ast.Node, push bool) bool) as func(n ast.Node, push bool, …go/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31