Recordsgolanggithub.com/envoyproxy/protoc-gen-validate
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
No recorded evidence matches these filters. Nothing is inferred; clear a filter to widen the slice.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.0.4
linux · go@1.26
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:0882784d80c20e919569b4a9a1a5ff54eb0aa7665750aedc7afd0bce723472f8
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/lyft/protoc-gen-star/v2 | v2.0.3 | CANDIDATE Correlated change; unproven combination | contract passed | 31 project-days |
| golang.org/x/net | v0.20.0 | CANDIDATE Correlated change; unproven combination | contract passed | 31 project-days |
| google.golang.org/protobuf | v1.32.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| google.golang.org/protobuf | v1.33.0 | CANDIDATE Correlated change; unproven combination | contract passed | 28 project-days |
| google.golang.org/protobuf | v1.34.2 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| github.com/iancoleman/strcase | v0.3.0 | PASS All observations passed | contract passed | 31 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.