Recordsgolanggoogle.golang.org/grpc
no sample at this coordinate yet
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
The cube reads the newest 6 versions and the first 10 symbols of each, so an empty cell here can mean "outside that window" rather than "never measured".
How to read the grid
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.83.1
linux · go@1.26
1 FAIL
· stage: PROJECT_TEST
· fingerprint: sha256:5139c3282f273ad81e98cc8f69ac04fbf0d940ece89888bc3422868a56278d60
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/cespare/xxhash/v2 | v2.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| github.com/cncf/xds/go | v0.0.0-20260202195803-dba9d589def2 | CANDIDATE Correlated change; unproven combination | nothing measured | 9 project-days |
| github.com/envoyproxy/go-control-plane | v0.14.0 | CANDIDATE Correlated change; unproven combination | contract passed | 8 project-days |
| github.com/envoyproxy/go-control-plane/envoy | v1.37.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 9 project-days |
| github.com/golang/glog | v1.2.5 | CANDIDATE Correlated change; unproven combination | contract passed | 8 project-days |
| github.com/golang/protobuf | v1.5.4 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| github.com/google/go-cmp | v0.7.0 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| github.com/google/uuid | v1.6.0 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| github.com/spiffe/go-spiffe/v2 | v2.7.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 8 project-days |
| go.opentelemetry.io/contrib/detectors/gcp | v1.44.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 8 project-days |
| go.opentelemetry.io/otel | v1.46.0 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| go.opentelemetry.io/otel/metric | v1.46.0 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| go.opentelemetry.io/otel/sdk | v1.46.0 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| go.opentelemetry.io/otel/sdk/metric | v1.46.0 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| go.opentelemetry.io/otel/trace | v1.46.0 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| golang.org/x/net | v0.58.0 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| golang.org/x/oauth2 | v0.36.0 | CANDIDATE Correlated change; unproven combination | contract passed | 8 project-days |
| golang.org/x/sync | v0.22.0 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| golang.org/x/sys | v0.47.0 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| gonum.org/v1/gonum | v0.17.0 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| google.golang.org/genproto/googleapis/rpc | v0.0.0-20260819154853-08b0e4226688 | CANDIDATE Correlated change; unproven combination | builds observed | 9 project-days |
| google.golang.org/protobuf | v1.36.12 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| cloud.google.com/go/auth | v0.18.2 | UNKNOWN No linked outcome measured | nothing measured | 9 project-days |
| cloud.google.com/go/compute/metadata | v0.9.0 | PASS All observations passed | contract passed | 9 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: 27 · unchanged at every release: 5
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.