Recordsgolanggolang.org/x/tools
Change the conditions
Current conditions
golang.org/x/tools/container/intsets.Sparse @v0.1.12x64 · go 1.26 · go
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
- Independent reporting peers
- 1
- Last recorded
- 2026-08-28
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
ubuntu glibc · x64 · go 1.26 · go 1
2 of 2 passed
Observed — real project builds reported from this coordinate.
-
alpine musl · x64 · go 1.26 · go · go
1 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.1.12
linux · go@1.26
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:8f959b6bebd85a593cf28df20bce331c6c103dbba62da82de88c1ed28c08d91d
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/yuin/goldmark | v1.4.13 | CANDIDATE Correlated change; unproven combination | nothing measured | 7 project-days |
| golang.org/x/mod | v0.6.0-dev.0.20220419223038-86c51ed26bb4 | CANDIDATE Correlated change; unproven combination | contract passed | 8 project-days |
| golang.org/x/net | v0.0.0-20220722155237-a158d28d115b | CANDIDATE Correlated change; unproven combination | nothing measured | 3 project-days |
| golang.org/x/net | v0.2.0 | CANDIDATE Correlated change; unproven combination | builds observed | 3 project-days |
| golang.org/x/net | v0.4.0 | CANDIDATE Correlated change; unproven combination | builds observed | 1 project-day |
| golang.org/x/sync | v0.0.0-20220722155255-886fb9371eb4 | CANDIDATE Correlated change; unproven combination | nothing measured | 6 project-days |
| golang.org/x/sync | v0.21.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| golang.org/x/sys | v0.0.0-20220722155257-8c9f86f7a55f | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| golang.org/x/sys | v0.2.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| golang.org/x/sys | v0.47.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| golang.org/x/text | v0.3.7 | PASS All observations passed | contract passed | 3 project-days |
| golang.org/x/text | v0.4.0 | PASS All observations passed | builds observed | 3 project-days |
| golang.org/x/text | v0.5.0 | PASS All observations passed | builds observed | 1 project-day |
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.