Recordsgolanggithub.com/envoyproxy/go-control-planev0.9.4
Change the conditions
Current conditions
github.com/envoyproxy/go-control-plane @v0.9.4debian 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
- 2
- Independent reporting peers
- 1
- Last recorded
- 2026-09-03
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/google/go-cmp | v0.4.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| github.com/google/go-cmp | v0.5.1 | CHANGED Version changed, no linked failure | nothing measured | 1 project-day |
| github.com/google/go-cmp | v0.7.0 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| google.golang.org/grpc | v1.28.0 | CHANGED Version changed, no linked failure | nothing measured | 1 project-day |
| google.golang.org/grpc | v1.31.0 | CHANGED Version changed, no linked failure | builds observed | 3 project-days |
| github.com/census-instrumentation/opencensus-proto | v0.2.1 | UNKNOWN No linked outcome measured | nothing measured | 4 project-days |
| github.com/envoyproxy/protoc-gen-validate | v0.1.0 | UNKNOWN No linked outcome measured | nothing measured | 4 project-days |
| github.com/golang/protobuf | v1.3.5 | UNKNOWN No linked outcome measured | nothing measured | 1 project-day |
| github.com/prometheus/client_model | v0.0.0-20190812154241-14fe0d1b01d4 | UNKNOWN No linked outcome measured | nothing measured | 2 project-days |
| google.golang.org/genproto | v0.0.0-20200331122359-1ee6d9798940 | UNKNOWN No linked outcome measured | nothing measured | 1 project-day |
| google.golang.org/genproto | v0.0.0-20200804131852-c06518451d9c | UNKNOWN No linked outcome measured | nothing measured | 1 project-day |
| github.com/cncf/udpa/go | v0.0.0-20191209042840-269d4d468f6f | PASS All observations passed | builds observed | 4 project-days |
| github.com/golang/protobuf | v1.4.2 | PASS All observations passed | contract passed | 1 project-day |
| github.com/golang/protobuf | v1.5.0 | PASS All observations passed | contract passed | 1 project-day |
| github.com/golang/protobuf | v1.5.2 | PASS All observations passed | contract passed | 1 project-day |
| github.com/prometheus/client_model | v0.6.2 | PASS All observations passed | contract passed | 1 project-day |
| github.com/prometheus/client_model | v0.6.3 | PASS All observations passed | builds observed | 1 project-day |
| google.golang.org/genproto | v0.0.0-20200825200019-8632dd797987 | PASS All observations passed | builds observed | 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: 2 · unchanged at every release: 12
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.