Recordsgolangmodernc.org/libc
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.74.4
windows · go@1.26
271 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/google/uuid | v1.6.0 | CANDIDATE Correlated change; unproven combination | contract passed | 14 project-days |
| github.com/mattn/go-isatty | v0.0.24 | CANDIDATE Correlated change; unproven combination | contract passed | 14 project-days |
| golang.org/x/sys | v0.47.0 | CANDIDATE Correlated change; unproven combination | contract passed | 14 project-days |
| golang.org/x/tools | v0.47.0 | CANDIDATE Correlated change; unproven combination | builds observed | 14 project-days |
| modernc.org/cc/v4 | v4.29.1 | CANDIDATE Correlated change; unproven combination | contract passed | 14 project-days |
| modernc.org/ccgo/v4 | v4.34.6 | CANDIDATE Correlated change; unproven combination | contract passed | 14 project-days |
| modernc.org/mathutil | v1.7.1 | CANDIDATE Correlated change; unproven combination | contract passed | 14 project-days |
| modernc.org/memory | v1.11.0 | CANDIDATE Correlated change; unproven combination | contract passed | 14 project-days |
| modernc.org/goabi0 | v0.2.0 | UNKNOWN No linked outcome measured | nothing measured | 14 project-days |
| github.com/dustin/go-humanize | v1.0.1 | PASS All observations passed | contract passed | 14 project-days |
| github.com/ncruces/go-strftime | v1.0.0 | PASS All observations passed | contract passed | 14 project-days |
| modernc.org/fileutil | v1.4.0 | PASS All observations passed | contract passed | 14 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: 8 · 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.