CodeSampleX

Recordsgolanggithub.com/prometheus/client_modelv0.6.2

Change the conditions
Fixed
OSwindows 11 Package versionv0.6.2 Architecturex64
Filter Runtimego 1.26 Symbolwhole package Package managergo 1 Clear filters

Current conditions

github.com/prometheus/client_model @v0.6.2windows 11 · x64 · go 1.26 · go 1

package-level total, not an API

7 of 9 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 (3)

Project observations
7 / 9
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Failures with a captured fingerprint
0 / 2
Last recorded
2026-08-18
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.2

linux · node@22.23 · moduleSystem=cjs · executionContext=node

5 FAIL · stage: UNKNOWN · fingerprint: sha256:88af852f99a8104e4bc3c23eea27ebf2990625ccabf45313970f5fd7fe56c4e2

View exact conditions View failure cluster
Library Version Health Measured there Projects
google.golang.org/protobuf v1.36.11 CANDIDATE Correlated change; unproven combination contract passed 14 project-days
google.golang.org/protobuf v1.36.12 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
google.golang.org/protobuf v1.36.6 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