CodeSampleX

Recordsgolangmodernc.org/cc/v4v4.29.0

Change the conditions
Fixed
Package versionv4.29.0 Package managergo
Filter OSdebian glibc Runtimego 1.26 Symbolwhole package Architecturex64 Execution contextgo libcglibc Clear filters

Current conditions

modernc.org/cc/v4 @v4.29.0debian 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

Unknown 1 · Steady 8

All 8 dependencies report steady passing evidence.

Library Version Health Measured there Projects
modernc.org/ccorpus2 v1.6.0 UNKNOWN No linked outcome measured nothing measured 3 project-days
github.com/dustin/go-humanize v1.0.1 PASS All observations passed contract passed 3 project-days
github.com/pbnjay/memory v0.0.0-20210728143218-7b4eea64cf58 PASS All observations passed contract passed 3 project-days
github.com/pmezard/go-difflib v1.0.0 PASS All observations passed contract passed 3 project-days
modernc.org/mathutil v1.7.1 PASS All observations passed contract passed 3 project-days
modernc.org/opt v0.2.0 PASS All observations passed contract passed 3 project-days
modernc.org/sortutil v1.2.1 PASS All observations passed contract passed 3 project-days
modernc.org/strutil v1.2.1 PASS All observations passed contract passed 3 project-days
modernc.org/token v1.1.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: 0 · unchanged at every release: 9

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.