CodeSampleX

Recordsgolangcel.dev/exprv0.19.1

Change the conditions
Fixed
OSubuntu glibc Package versionv0.19.1 Package managergo 1
Filter Runtimego 1.26 Symbolwhole package Architecturex64 libcglibc Clear filters

Current conditions

cel.dev/expr @v0.19.1ubuntu glibc · 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
Usage records
2
Independent reporting peers
2
Last recorded
2026-08-26

Dependency Health

Observed combinations and failure evidence for this release

Changed 4 · Steady 0

Dependency changes observed: 4. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
google.golang.org/genproto/googleapis/rpc v0.0.0-20240826202546-f6391c0de4c7 CHANGED Version changed, no linked failure contract passed 1 project-day
google.golang.org/genproto/googleapis/rpc v0.0.0-20241007155032-5fefd90f89a9 CHANGED Version changed, no linked failure contract passed 1 project-day
google.golang.org/protobuf v1.34.2 CHANGED Version changed, no linked failure contract passed 1 project-day
google.golang.org/protobuf v1.35.1 CHANGED Version changed, no linked failure contract passed 1 project-day

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: 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.