CodeSampleX

Recordsgolangcloud.google.com/go/authv0.18.2cloud.google.com/go/auth.New2LOTokenProvider

Change the conditions
Fixed
Package versionv0.18.2 Symbolcloud.google.com/go/auth.New2LOTokenProvider
Filter OSubuntu glibc Runtimego 1.26 Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

cloud.google.com/go/auth.New2LOTokenProvider @v0.18.2ubuntu glibc · x64 · go 1.26 · go 1

2 of 2 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
2 / 2
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-10-10

Dependency Health

Observed combinations and failure evidence for this release

Changed 22 · Steady 0

Dependency changes observed: 22. 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 10 project-days
github.com/google/go-cmp v0.7.0 CHANGED Version changed, no linked failure contract passed 10 project-days
github.com/google/s2a-go v0.1.9 CHANGED Version changed, no linked failure contract passed 10 project-days
github.com/googleapis/enterprise-certificate-proxy v0.3.11 CHANGED Version changed, no linked failure builds observed 4 project-days
github.com/googleapis/enterprise-certificate-proxy v0.3.14 CHANGED Version changed, no linked failure builds observed 6 project-days
github.com/googleapis/gax-go/v2 v2.17.0 CHANGED Version changed, no linked failure builds observed 4 project-days
github.com/googleapis/gax-go/v2 v2.21.0 CHANGED Version changed, no linked failure builds observed 6 project-days
go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.61.0 CHANGED Version changed, no linked failure nothing measured 10 project-days
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.61.0 CHANGED Version changed, no linked failure builds observed 10 project-days
go.opentelemetry.io/otel v1.39.0 CHANGED Version changed, no linked failure builds observed 4 project-days
go.opentelemetry.io/otel v1.43.0 CHANGED Version changed, no linked failure contract passed 6 project-days
go.opentelemetry.io/otel/sdk v1.39.0 CHANGED Version changed, no linked failure nothing measured 4 project-days
go.opentelemetry.io/otel/sdk v1.43.0 CHANGED Version changed, no linked failure contract passed 6 project-days
go.opentelemetry.io/otel/trace v1.39.0 CHANGED Version changed, no linked failure builds observed 4 project-days
go.opentelemetry.io/otel/trace v1.43.0 CHANGED Version changed, no linked failure contract passed 6 project-days
golang.org/x/net v0.49.0 CHANGED Version changed, no linked failure contract passed 4 project-days
golang.org/x/net v0.52.0 CHANGED Version changed, no linked failure contract passed 6 project-days
golang.org/x/time v0.14.0 CHANGED Version changed, no linked failure nothing measured 4 project-days
golang.org/x/time v0.15.0 CHANGED Version changed, no linked failure contract passed 6 project-days
google.golang.org/grpc v1.78.0 CHANGED Version changed, no linked failure builds observed 4 project-days
google.golang.org/grpc v1.80.0 CHANGED Version changed, no linked failure contract passed 6 project-days
google.golang.org/protobuf v1.36.11 CHANGED Version changed, no linked failure contract passed 10 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: 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.