Recordsgolangmodernc.org/libcv1.22.5
Change the conditions
Current conditions
modernc.org/libc @v1.22.5windows · x64 · go 1.26 · go 1
package-level total, not an API
3 of 3 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (1)
- Project observations
- 3 / 3
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-17
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.22.5
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:5299cca1c440bf07bc38e84fef5b85ae3213905355fe5dd433e106a2ba76d8a5
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/google/uuid | v1.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| github.com/mattn/go-isatty | v0.0.17 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| golang.org/x/sys | v0.7.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| modernc.org/mathutil | v1.5.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| modernc.org/memory | v1.5.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| github.com/dustin/go-humanize | v1.0.1 | PASS All observations passed | 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.
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.