Recordsgolangmodernc.org/gc/v3
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
v3.1.4
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:21897755ae0694d17ad1ef575ea85e5b7bc3e64c924425988aa3e787e9b5fea0
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/tools | v0.31.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| golang.org/x/tools | v0.46.0 | CANDIDATE Correlated change; unproven combination | builds observed | 3 project-days |
| golang.org/x/tools | v0.47.0 | CANDIDATE Correlated change; unproven combination | builds observed | 11 project-days |
| golang.org/x/exp | v0.0.0-20250305212735-054e65f0b394 | UNKNOWN No linked outcome measured | nothing measured | 2 project-days |
| modernc.org/ebnfutil | v1.1.0 | UNKNOWN No linked outcome measured | nothing measured | 5 project-days |
| github.com/dustin/go-humanize | v1.0.1 | PASS All observations passed | contract passed | 16 project-days |
| github.com/hashicorp/golang-lru/v2 | v2.0.7 | PASS All observations passed | contract passed | 16 project-days |
| github.com/pmezard/go-difflib | v1.0.0 | PASS All observations passed | contract passed | 5 project-days |
| golang.org/x/exp | v0.0.0-20251023183803-a4bb9ffd2546 | PASS All observations passed | contract passed | 3 project-days |
| modernc.org/mathutil | v1.7.1 | PASS All observations passed | contract passed | 16 project-days |
| modernc.org/strutil | v1.2.1 | PASS All observations passed | contract passed | 16 project-days |
| modernc.org/token | v1.1.0 | PASS All observations passed | contract passed | 16 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: 1 · unchanged at every release: 8
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.