Recordsgolangcloud.google.com/go/authv0.24.1cloud.google.com/go/auth.AuthorizationHandlerOptions
Change the conditions
Current conditions
cloud.google.com/go/auth.AuthorizationHandlerOptions @v0.24.1debian glibc · x64 · go 1.26 · go · go
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-10-14
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 15. 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 | 18 project-days |
| github.com/google/go-cmp | v0.7.0 | CHANGED Version changed, no linked failure | contract passed | 18 project-days |
| github.com/google/s2a-go | v0.1.9 | CHANGED Version changed, no linked failure | contract passed | 18 project-days |
| github.com/googleapis/enterprise-certificate-proxy | v0.3.17 | CHANGED Version changed, no linked failure | contract passed | 18 project-days |
| github.com/googleapis/gax-go/v2 | v2.26.2 | CHANGED Version changed, no linked failure | contract passed | 18 project-days |
| go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc | v0.67.0 | CHANGED Version changed, no linked failure | contract passed | 18 project-days |
| go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp | v0.67.0 | CHANGED Version changed, no linked failure | contract passed | 18 project-days |
| go.opentelemetry.io/otel | v1.45.0 | CHANGED Version changed, no linked failure | contract passed | 18 project-days |
| go.opentelemetry.io/otel/sdk | v1.45.0 | CHANGED Version changed, no linked failure | contract passed | 18 project-days |
| go.opentelemetry.io/otel/trace | v1.45.0 | CHANGED Version changed, no linked failure | contract passed | 18 project-days |
| golang.org/x/net | v0.58.0 | CHANGED Version changed, no linked failure | contract passed | 18 project-days |
| google.golang.org/api | v0.288.0 | CHANGED Version changed, no linked failure | contract passed | 18 project-days |
| google.golang.org/genproto/googleapis/rpc | v0.0.0-20260715232425-e75dac1f907d | CHANGED Version changed, no linked failure | contract passed | 18 project-days |
| google.golang.org/grpc | v1.83.2 | CHANGED Version changed, no linked failure | contract passed | 18 project-days |
| google.golang.org/protobuf | v1.36.11 | CHANGED Version changed, no linked failure | contract passed | 18 project-days |
| golang.org/x/time | v0.15.0 | PASS All observations passed | contract passed | 18 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: 15 · unchanged at every release: 1
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.