CodeSampleX

Recordsgolangcloud.google.com/go/compute/metadatav0.9.0

Change the conditions
Fixed
OSlinux Package versionv0.9.0 Package managergo
Filter Runtimego 1.26 Symbolwhole package Architecturex64 Execution contextgo libcmusl Clear filters

Current conditions

cloud.google.com/go/compute/metadata @v0.9.0linux · 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 1 · Steady 1

First observed break

v0.9.0

linux · go@1.26

1 FAIL · stage: UNKNOWN · fingerprint: sha256:f3a5a30110770e510159fdb2eda104f320d4f31f36251c1770da6e4ec58af6d8

View exact conditions View failure cluster
Library Version Health Measured there Projects
golang.org/x/sys v0.45.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
github.com/google/go-cmp v0.7.0 PASS All observations passed contract passed 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.

Libraryv0.9.0v0.5.0
golang.org/x/sys v0.45.0 v0.31.0
github.com/google/go-cmp v0.7.0 —

Moved: 1 · 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