Recordsgolanggithub.com/prometheus/client_modelv0.6.3
Change the conditions
Current conditions
github.com/prometheus/client_model @v0.6.3debian 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
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-01
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| google.golang.org/protobuf | v1.36.12 | contract passed | 1 project-day |
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.
| Library | v0.6.3 | v0.6.2 | v0.2.0 |
|---|---|---|---|
| google.golang.org/protobuf | v1.36.12 | v1.36.6 | — |
| github.com/golang/protobuf | — | — | v1.5.4 |
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
-
observed PROJECT_RESOLVE exit 1 ×1 v0.6.3 os=linux · runtime=go@1.26 sha256:6bcd37b43ee2…<path>:<n>:<n>: missing go.sum entry for module providing package github.com/golang/protobuf/proto (imported by …go/module · resolve-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01