Recordsgolanggoogle.golang.org/apiv0.274.0
Change the conditions
Current conditions
google.golang.org/api @v0.274.0linux · glibc · x64 · go 1.26 · go 1
package-level total, not an API
15 of 15 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 15 / 15
- 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
Dependency changes observed: 17. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| cloud.google.com/go/auth | v0.18.2 | CHANGED Version changed, no linked failure | contract passed | 6 project-days |
| cloud.google.com/go/auth/oauth2adapt | v0.2.8 | CHANGED Version changed, no linked failure | contract passed | 6 project-days |
| cloud.google.com/go/compute/metadata | v0.9.0 | CHANGED Version changed, no linked failure | contract passed | 6 project-days |
| github.com/google/go-cmp | v0.7.0 | CHANGED Version changed, no linked failure | contract passed | 6 project-days |
| github.com/google/s2a-go | v0.1.9 | CHANGED Version changed, no linked failure | contract passed | 6 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.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 | 6 project-days |
| go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp | v0.61.0 | CHANGED Version changed, no linked failure | contract passed | 6 project-days |
| golang.org/x/net | v0.52.0 | CHANGED Version changed, no linked failure | contract passed | 6 project-days |
| golang.org/x/oauth2 | v0.36.0 | CHANGED Version changed, no linked failure | contract passed | 6 project-days |
| golang.org/x/sync | v0.20.0 | CHANGED Version changed, no linked failure | contract passed | 6 project-days |
| golang.org/x/time | v0.15.0 | CHANGED Version changed, no linked failure | contract passed | 6 project-days |
| google.golang.org/genproto/googleapis/bytestream | v0.0.0-20260319201613-d00831a3d3e7 | CHANGED Version changed, no linked failure | nothing measured | 5 project-days |
| google.golang.org/genproto/googleapis/rpc | v0.0.0-20260401001100-f93e5f3e9f0f | CHANGED Version changed, no linked failure | builds observed | 6 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 | 6 project-days |
| github.com/google/uuid | v1.6.0 | PASS All observations passed | contract passed | 5 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: 22 · unchanged at every release: 3
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.