CodeSampleX

Recordsgolanggithub.com/envoyproxy/protoc-gen-validatev1.3.3

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

Current conditions

github.com/envoyproxy/protoc-gen-validate @v1.3.3debian 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
2
Independent reporting peers
1
Last recorded
2026-10-11

Dependency Health

Observed combinations and failure evidence for this release

Changed 5 · Steady 1

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

Library Version Health Measured there Projects
github.com/lyft/protoc-gen-star/v2 v2.0.4 CHANGED Version changed, no linked failure nothing measured 2 project-days
golang.org/x/net v0.49.0 CHANGED Version changed, no linked failure contract passed 2 project-days
golang.org/x/net v0.58.0 CHANGED Version changed, no linked failure contract passed 2 project-days
google.golang.org/protobuf v1.36.11 CHANGED Version changed, no linked failure contract passed 3 project-days
google.golang.org/protobuf v1.36.12 CHANGED Version changed, no linked failure contract passed 1 project-day
github.com/iancoleman/strcase v0.3.0 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: 3 · unchanged at every release: 1

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.