CodeSampleX

Recordsgolangcloud.google.com/go/kmsv1.31.0

Change the conditions
Fixed
Package versionv1.31.0 Package managergo
Filter OSalpine musl Runtimego 1.26 Symbolwhole package Architecturex64 Execution contextgo libcmusl Clear filters

Current conditions

cloud.google.com/go/kms @v1.31.0alpine musl · x64 · go 1.26 · go · go

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-08-31
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 8 · Steady 0

First observed break

v1.31.0

linux · go@1.26

1 FAIL · stage: UNKNOWN · fingerprint: sha256:042f6e977a16262a7e633b3137ce9291be598b66496d9201e447ee2b8efa6eb8

View exact conditions View failure cluster
Library Version Health Measured there Projects
cloud.google.com/go/iam v1.7.0 CANDIDATE Correlated change; unproven combination 2 project-days
cloud.google.com/go/longrunning v0.9.0 CANDIDATE Correlated change; unproven combination 2 project-days
github.com/googleapis/gax-go/v2 v2.22.0 CANDIDATE Correlated change; unproven combination 2 project-days
google.golang.org/api v0.277.0 CANDIDATE Correlated change; unproven combination 2 project-days
google.golang.org/genproto v0.0.0-20260319201613-d00831a3d3e7 CANDIDATE Correlated change; unproven combination 2 project-days
google.golang.org/genproto/googleapis/api v0.0.0-20260406210006-6f92a3bedf2d CANDIDATE Correlated change; unproven combination 2 project-days
google.golang.org/grpc v1.81.0 CANDIDATE Correlated change; unproven combination 2 project-days
google.golang.org/protobuf v1.36.11 CANDIDATE Correlated change; unproven combination 2 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.

Libraryv1.35.0v1.34.0v1.31.0v1.15.8
cloud.google.com/go/iam v1.11.0 v1.11.0 v1.7.0 v1.1.7
cloud.google.com/go/longrunning v1.2.0 v1.2.0 v0.9.0 —
github.com/googleapis/gax-go/v2 v2.23.0 v2.23.0 v2.22.0 v2.12.3
google.golang.org/api v0.287.1 v0.293.0 v0.277.0 v0.176.0
google.golang.org/genproto v0.0.0-20260319201613-d00831a3d3e7 v0.0.0-20260319201613-d00831a3d3e7 v0.0.0-20260319201613-d00831a3d3e7 v0.0.0-20240227224415-6ceb2ff114de
google.golang.org/genproto/googleapis/api v0.0.0-20260630182238-925bb5da69e7 v0.0.0-20260706201446-f0a921348800 v0.0.0-20260406210006-6f92a3bedf2d v0.0.0-20240401170217-c3f982113cda
google.golang.org/grpc v1.83.2 v1.84.0 v1.81.0 v1.63.2
google.golang.org/protobuf v1.36.12 v1.36.12 v1.36.11 v1.33.0
go.opentelemetry.io/otel/trace v1.44.0 v1.44.0 — —

Moved: 8 · 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.

Recent failure clusters