Recordsgolanghonnef.co/go/tools
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
No recorded evidence matches these filters. Nothing is inferred; clear a filter to widen the slice.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.0.1-2019.2.3
linux · go@1.26
1 FAIL
· stage: PROJECT_RESOLVE
· fingerprint: sha256:5e7f0af5c9d3e37618b4ebba71c10942833c38e6fb0081a8f076b2227a19c837
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/mod | v0.0.0-20190513183733-4bf6d317e70e | CANDIDATE Correlated change; unproven combination | builds observed | 6 project-days |
| golang.org/x/mod | v0.1.1-0.20191105210325-c90efee705ee | CANDIDATE Correlated change; unproven combination | builds observed | 6 project-days |
| golang.org/x/mod | v0.8.0 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| golang.org/x/tools | v0.0.0-20190621195816-6e04913cbbac | CANDIDATE Correlated change; unproven combination | builds observed | 1 project-day |
| golang.org/x/tools | v0.0.0-20191029190741-b9c20aec41a5 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| golang.org/x/tools | v0.0.0-20200103221440-774c71fcf114 | CANDIDATE Correlated change; unproven combination | builds observed | 6 project-days |
| golang.org/x/tools | v0.6.0 | CANDIDATE Correlated change; unproven combination | contract passed | 10 project-days |
| github.com/google/renameio | v0.1.0 | UNKNOWN No linked outcome measured | nothing measured | 22 project-days |
| github.com/kisielk/gotool | v1.0.0 | UNKNOWN No linked outcome measured | nothing measured | 22 project-days |
| github.com/BurntSushi/toml | v0.3.1 | PASS All observations passed | contract passed | 21 project-days |
| github.com/rogpeppe/go-internal | v1.3.0 | PASS All observations passed | contract passed | 22 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: 2 · 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.