CodeSampleX

Recordsgolanggithub.com/prometheus/client_model

Change the conditions
Fixed
OSdebian glibc Runtimego 1.26 Package versionv0.6.2
Filter Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

github.com/prometheus/client_model @v0.6.2debian glibc · x64 · go 1.26 · go · go

2 of 2 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (3)

Project observations
8 / 8
Contract verifications
2 / 2
Usage records
11
Independent reporting peers
1
Last recorded
2026-09-14

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

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 · executionContext=node · moduleSystem=cjs

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

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.