Recordsgolanghonnef.co/go/tools
no sample at this coordinate yet
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
How to read the grid
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.0.1-2020.1.4
linux · go@1.26
2 FAIL
· stage: PROJECT_RESOLVE
· fingerprint: sha256:960c448010d338b23e4225acf905c3ba5fc46c4e38004ca42dccb0ec225d0a82
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/mod | v0.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| golang.org/x/tools | v0.0.0-20200618134242-20370b0cb4b2 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| golang.org/x/tools | v0.0.0-20200804011535-6c149bb5ef0d | CANDIDATE Correlated change; unproven combination | builds observed | 2 project-days |
| github.com/google/renameio | v0.1.0 | UNKNOWN No linked outcome measured | nothing measured | 3 project-days |
| github.com/kisielk/gotool | v1.0.0 | UNKNOWN No linked outcome measured | nothing measured | 3 project-days |
| github.com/BurntSushi/toml | v0.3.1 | PASS All observations passed | contract passed | 3 project-days |
| github.com/rogpeppe/go-internal | v1.3.0 | PASS All observations passed | contract passed | 3 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.