CodeSampleX

Recordsgolanggithub.com/prometheus/client_modelv0.6.1github.com/prometheus/client_model/go.LabelPair

Change the conditions
Fixed
OSubuntu glibc Package versionv0.6.1 Symbolgithub.com/prometheus/client_model/go.LabelPair
Filter Runtimego 1.26 Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

github.com/prometheus/client_model/go.LabelPair @v0.6.1ubuntu glibc · x64 · go 1.26 · go 1

16 of 16 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
16 / 16
Contract verifications
nothing at this coordinate
Independent reporting peers
2
Last recorded
2026-09-05
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 0

First observed break

v0.6.1

linux · go@1.26

1 FAIL · stage: PROJECT_RESOLVE · fingerprint: sha256:41c0bdc4aec8568b43c029357bc89b673b870e4168177a899c9eb8bfaab5e79c

View exact conditions View failure cluster
Library Version Health Measured there Projects
google.golang.org/protobuf v1.33.0 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
google.golang.org/protobuf v1.34.2 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
google.golang.org/protobuf v1.36.12 CANDIDATE Correlated change; unproven combination 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.6.3v0.6.2v0.6.1v0.5.0v0.2.0v0.0.0-20190812154241-14fe0d1b01d4
github.com/golang/protobuf — — — — v1.5.4 v1.3.5
google.golang.org/protobuf v1.36.12 v1.36.6 v1.36.12 v1.35.1 — —

Moved: 2 · unchanged at every release: 0

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