CodeSampleX

Recordsgolangcloud.google.com/go/auth

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.

Fixed
Package versionv0.23.0 Symbolwhole package
Filter Runtimego 1.26 Architecturex64 Execution contextgo libcglibc Clear filters
OS × Package manager
○ 22026-10-09
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

Changed 16 · Steady 0

Dependency changes observed: 16. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
cloud.google.com/go/compute/metadata v0.9.0 CHANGED Version changed, no linked failure contract passed 1 project-day
github.com/google/go-cmp v0.7.0 CHANGED Version changed, no linked failure contract passed 1 project-day
github.com/google/s2a-go v0.1.9 CHANGED Version changed, no linked failure contract passed 1 project-day
github.com/googleapis/enterprise-certificate-proxy v0.3.20 CHANGED Version changed, no linked failure builds observed 1 project-day
github.com/googleapis/gax-go/v2 v2.23.0 CHANGED Version changed, no linked failure contract passed 1 project-day
go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.67.0 CHANGED Version changed, no linked failure builds observed 1 project-day
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.69.0 CHANGED Version changed, no linked failure builds observed 1 project-day
go.opentelemetry.io/otel v1.44.0 CHANGED Version changed, no linked failure contract passed 1 project-day
go.opentelemetry.io/otel/sdk v1.44.0 CHANGED Version changed, no linked failure builds observed 1 project-day
go.opentelemetry.io/otel/trace v1.44.0 CHANGED Version changed, no linked failure contract passed 1 project-day
golang.org/x/net v0.58.0 CHANGED Version changed, no linked failure contract passed 1 project-day
golang.org/x/time v0.15.0 CHANGED Version changed, no linked failure contract passed 1 project-day
google.golang.org/api v0.293.0 CHANGED Version changed, no linked failure contract passed 1 project-day
google.golang.org/genproto/googleapis/rpc v0.0.0-20260807164820-c8921c73eeea CHANGED Version changed, no linked failure builds observed 1 project-day
google.golang.org/grpc v1.84.0 CHANGED Version changed, no linked failure contract passed 1 project-day
google.golang.org/protobuf v1.36.12 CHANGED Version changed, no linked failure contract passed 1 project-day

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: 16 · unchanged at every release: 0

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.