CodeSampleX

Recordsgolanggithub.com/prometheus/client_modelv0.0.0-20190812154241-14fe0d1b01d4

Change the conditions
Fixed
Package versionv0.0.0-20190812154241-14fe0d1b01d4 Symbolwhole package
Filter OSdebian glibc Runtimego 1.26 Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

github.com/prometheus/client_model @v0.0.0-20190812154241-14fe0d1b01d4debian glibc · 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
4
Independent reporting peers
1
Last recorded
2026-10-09

Dependency Health

Observed combinations and failure evidence for this release

Changed 2 · Steady 0

Dependency changes observed: 2. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
github.com/golang/protobuf v1.3.5 CHANGED Version changed, no linked failure builds observed 2 project-days
github.com/golang/protobuf v1.4.2 CHANGED Version changed, no linked failure contract passed 5 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.