Recordsgolangmodernc.org/memory
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
v1.5.0
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:5299cca1c440bf07bc38e84fef5b85ae3213905355fe5dd433e106a2ba76d8a5
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| modernc.org/mathutil | v1.5.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 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.
| Library | v1.12.0 | v1.11.0 | v1.5.0 |
|---|---|---|---|
| golang.org/x/sys | v0.47.0 | v0.46.0 | — |
| modernc.org/mathutil | v1.7.1 | v1.7.1 | v1.5.0 |
Moved: 2 · unchanged at every release: 0
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.