kmsv1.35.0

Which symbol ran where

Symbols × operating systems for this version. Cells drill into the package's compatibility cube.

6 1○ 52026-10-10

	debian glibc	ubuntu glibc
cloud.google.com/go/kms/apiv1/kmspb.CryptoKey	100%2	100%9
cloud.google.com/go/kms/apiv1/kmspb.CryptoKeyVersion	100%2	100%16
cloud.google.com/go/kms/apiv1/kmspb.CryptoKeyVersionTemplate	100%2	100%16
cloud.google.com/go/kms/apiv1/kmspb.CryptoKeyVersion_CRYPTO_KEY_VERSION_ALGORITHM_UNSPECIFIED	100%2	100%11
cloud.google.com/go/kms/apiv1/kmspb.CryptoKeyVersion_CryptoKeyVersionAlgorithm	100%2	100%10
cloud.google.com/go/kms/apiv1/kmspb.CryptoKeyVersion_CryptoKeyVersionAlgorithm_name	100%2	100%9

Showing the environments with the most evidence.

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.

Environment detail

Project-level observations and symbol/contract verifications are counted separately and never combined.

These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.

Environment	Confidence	Observations	Verified	Pass rate	Peers	Last seen
go 1.26 · Go · go · linux glibc · docker Observations: PROJECT_COMPILE 4✓ · PROJECT_LOAD 10✓ · PROJECT_TEST 10✓ — Usage: USED 10✓ — Verified: CONTRACT 24✓	LOW	24 +10	24	100%	1 · 1✓	2026-10-10
go 1.26 · Go · go · linux glibc Observations: PROJECT_COMPILE 2✓ · PROJECT_PROCESS 42✓ · PROJECT_TEST 2✓ — Usage: USED 22✓ — Verified: UNKNOWN 0✓ 1✕	LOW	46 +22	1	98%	1	2026-10-10

Recent failure clusters

observed UNKNOWN exit 1 Evidence gap ×1 v1.35.0 os=linux · runtime=go@1.26 cloud.google.com/go/kms/apiv1/kmspb.CryptoKey sha256:a7b4cd6016d4…
# <token> · <path>:<n>:<n>: could not import math/bits (open <path>: no such file or directory) · # <token> …
go · unclassified-diagnostic · outer go run · gap stage-unknown

Evidence quality: complete · Environment variants: 1 · First recorded: 2026-10-10 · Last seen: 2026-10-10

Diagnostic re-verification candidate

Where does this failure start and stop?

Records/golang/cloud.google.com/go/kms/v1.35.0

Which symbol ran where

Environment detail

Recent failure clusters

Symbols

Records golang cloud.google.com/go/kmsv1.35.0