Recordsgolanggithub.com/envoyproxy/go-control-planev0.9.0
Change the conditions
Current conditions
github.com/envoyproxy/go-control-plane @v0.9.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
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-10-13
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 5. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/envoyproxy/protoc-gen-validate | v0.1.0 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| github.com/golang/protobuf | v1.3.2 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| github.com/prometheus/client_model | v0.0.0-20190812154241-14fe0d1b01d4 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| google.golang.org/genproto | v0.0.0-20190819201941-24fa4b261c55 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| google.golang.org/grpc | v1.25.1 | CHANGED Version changed, no linked failure | builds observed | 2 project-days |
| github.com/census-instrumentation/opencensus-proto | v0.2.1 | UNKNOWN No linked outcome measured | nothing measured | 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: 6 · unchanged at every release: 8
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.