Recordsgolanggithub.com/json-iterator/go
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
Showing the environments with the most evidence. The cube reads the newest 6 versions and the first 10 symbols of each, so an empty cell here can mean "outside that window" rather than "never measured".
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
v1.1.11
linux · go@1.26
1 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:964ddac6b19a356d0ae3f5727559d1fc36ac1222ed1964d18326e8a89565fde3
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/modern-go/concurrent | v0.0.0-20180228061459-e0a39a4cb421 | CANDIDATE Correlated change; unproven combination | contract passed | 13 project-days |
| github.com/modern-go/concurrent | v0.0.0-20180306012644-bacd9c7ef1dd | CANDIDATE Correlated change; unproven combination | builds observed | 14 project-days |
| github.com/modern-go/reflect2 | v0.0.0-20180701023420-4b7aa43c6742 | CANDIDATE Correlated change; unproven combination | contract passed | 12 project-days |
| github.com/modern-go/reflect2 | v1.0.1 | CANDIDATE Correlated change; unproven combination | nothing measured | 14 project-days |
| github.com/modern-go/reflect2 | v1.0.2 | CANDIDATE Correlated change; unproven combination | builds observed | 1 project-day |
| github.com/stretchr/testify | v1.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 13 project-days |
| github.com/stretchr/testify | v1.4.0 | CANDIDATE Correlated change; unproven combination | contract passed | 14 project-days |
| github.com/google/gofuzz | v1.0.0 | UNKNOWN No linked outcome measured | nothing measured | 27 project-days |
| github.com/davecgh/go-spew | v1.1.1 | PASS All observations passed | contract passed | 27 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: 3 · 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.