Recordsgolanggithub.com/envoyproxy/protoc-gen-validatev1.0.4github.com/envoyproxy/protoc-gen-validate/validate.FieldRules
Change the conditions
Current conditions
github.com/envoyproxy/protoc-gen-validate/validate.FieldRules @v1.0.4linux · glibc · x64 · go 1.26 · go 1
1 of 1 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-09-19
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 4. 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.3 | CHANGED Version changed, no linked failure | builds observed | 13 project-days |
| golang.org/x/net | v0.20.0 | CHANGED Version changed, no linked failure | contract passed | 13 project-days |
| google.golang.org/protobuf | v1.32.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| google.golang.org/protobuf | v1.33.0 | CHANGED Version changed, no linked failure | contract passed | 12 project-days |
| github.com/iancoleman/strcase | v0.3.0 | PASS All observations passed | contract passed | 13 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.