Recordsgolanggithub.com/prometheus/client_golangv1.11.0github.com/prometheus/client_golang/prometheus.Counter
Change the conditions
Current conditions
github.com/prometheus/client_golang/prometheus.Counter @v1.11.0debian glibc · x64 · go 1.26 · go · go
1 of 1 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 (1)
- Project observations
- 1 / 1
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-16
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.11.0
linux · go@1.26
2 FAIL
· stage: PROJECT_RESOLVE
· fingerprint: sha256:ebc5ddd015717eb4406f37af8bb31a2a7ce7d43cfd4dbb218a18e48f0cd90f68
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/cespare/xxhash/v2 | v2.1.1 | CANDIDATE Correlated change; unproven combination | contract passed | 12 project-days |
| github.com/cespare/xxhash/v2 | v2.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| github.com/golang/protobuf | v1.4.3 | CANDIDATE Correlated change; unproven combination | contract passed | 12 project-days |
| github.com/golang/protobuf | v1.5.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| github.com/json-iterator/go | v1.1.11 | CANDIDATE Correlated change; unproven combination | contract passed | 14 project-days |
| github.com/prometheus/client_model | v0.2.0 | CANDIDATE Correlated change; unproven combination | contract passed | 12 project-days |
| github.com/prometheus/client_model | v0.6.2 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| github.com/prometheus/common | v0.26.0 | CANDIDATE Correlated change; unproven combination | contract passed | 12 project-days |
| github.com/prometheus/common | v0.32.1 | CANDIDATE Correlated change; unproven combination | builds observed | 2 project-days |
| github.com/prometheus/procfs | v0.21.1 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| github.com/prometheus/procfs | v0.6.0 | CANDIDATE Correlated change; unproven combination | contract passed | 12 project-days |
| golang.org/x/sys | v0.0.0-20210603081109-ebe580a85c40 | CANDIDATE Correlated change; unproven combination | contract passed | 12 project-days |
| golang.org/x/sys | v0.47.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| github.com/beorn7/perks | v1.0.1 | PASS All observations passed | contract passed | 14 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.
Moved: 9 · unchanged at every release: 5
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 ×2 v1.11.0 os=linux · runtime=go@1.26 sha256:ebc5ddd01571…<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-03 · Last seen: 2026-09-03