Recordsgolangmodernc.org/libcv1.73.5
Change the conditions
Current conditions
modernc.org/libc @v1.73.5linux · glibc · x64 · go 1.26 · go · go
package-level total, not an API
Recorded as present in projects. Nothing was run at this coordinate.
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-16
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 8. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/google/uuid | v1.6.0 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| github.com/mattn/go-isatty | v0.0.20 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| golang.org/x/sys | v0.46.0 | CHANGED Version changed, no linked failure | builds observed | 3 project-days |
| golang.org/x/tools | v0.46.0 | CHANGED Version changed, no linked failure | builds observed | 3 project-days |
| modernc.org/cc/v4 | v4.29.0 | CHANGED Version changed, no linked failure | builds observed | 3 project-days |
| modernc.org/ccgo/v4 | v4.34.6 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| modernc.org/mathutil | v1.7.1 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| modernc.org/memory | v1.11.0 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| modernc.org/goabi0 | v0.2.0 | UNKNOWN No linked outcome measured | nothing measured | 1 project-day |
| github.com/dustin/go-humanize | v1.0.1 | PASS All observations passed | contract passed | 3 project-days |
| github.com/ncruces/go-strftime | v1.0.0 | PASS All observations passed | contract passed | 3 project-days |
| modernc.org/fileutil | v1.4.0 | PASS All observations passed | contract passed | 3 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.