CodeSampleX

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

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

Current conditions

github.com/envoyproxy/protoc-gen-validate @v1.3.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
3
Independent reporting peers
1
Last recorded
2026-10-11
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 7 · Steady 1

First observed break

v1.3.0

linux · go@1.26

1 FAIL · stage: PROJECT_RESOLVE · fingerprint: sha256:4b0da8d406c3fd2094fd9e987d083994aeb882c2677a435aa8d44174037fd8b7

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/lyft/protoc-gen-star/v2 v2.0.4-0.20230330145011-496ad1ac90a4 CANDIDATE Correlated change; unproven combination nothing measured 22 project-days
golang.org/x/net v0.35.0 CANDIDATE Correlated change; unproven combination builds observed 1 project-day
golang.org/x/net v0.42.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
golang.org/x/net v0.47.0 CANDIDATE Correlated change; unproven combination contract passed 20 project-days
google.golang.org/protobuf v1.36.10 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
google.golang.org/protobuf v1.36.11 CANDIDATE Correlated change; unproven combination contract passed 20 project-days
google.golang.org/protobuf v1.36.12 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
github.com/iancoleman/strcase v0.3.0 PASS All observations passed contract passed 22 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.

Libraryv1.3.3v1.3.0v1.2.1v1.0.4
github.com/lyft/protoc-gen-star/v2 v2.0.4 v2.0.4-0.20230330145011-496ad1ac90a4 v2.0.4-0.20230330145011-496ad1ac90a4 v2.0.3
golang.org/x/net v0.49.0 v0.42.0 v0.34.0 v0.20.0
google.golang.org/protobuf v1.36.12 v1.36.12 v1.36.10 v1.32.0
github.com/iancoleman/strcase v0.3.0 v0.3.0 v0.3.0 v0.3.0

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.

Recent failure clusters