CodeSampleX

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

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

Current conditions

github.com/envoyproxy/protoc-gen-validate @v1.2.1ubuntu glibc · x64 · go 1.26 · go 1

package-level total, not an API

0 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed

Project observations
40 / 40
Contract verifications
0 / 1
Usage records
20
Independent reporting peers
1
Last recorded
2026-09-15

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Unknown 1 · Steady 0

First observed break

v1.2.1

linux · go@1.26

1 FAIL · stage: UNKNOWN · fingerprint: sha256:f9232a56ee73a8c02f213399622f3bfbbd5e586b486a9b9004a63533e2adb49f

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 24 project-days
golang.org/x/net v0.42.0 CANDIDATE Correlated change; unproven combination contract passed 25 project-days
google.golang.org/protobuf v1.36.10 CANDIDATE Correlated change; unproven combination contract passed 25 project-days
github.com/iancoleman/strcase v0.3.0 UNKNOWN No linked outcome measured nothing measured 24 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.

Recent failure clusters