CodeSampleX

Recordsgolanggithub.com/prometheus/procfsv0.21.1

Change the conditions
Fixed
Package versionv0.21.1 Package managergo 1
Filter OSubuntu glibc Runtimego 1.26 Symbolwhole package Architecturex64 libcglibc Clear filters

Current conditions

github.com/prometheus/procfs @v0.21.1ubuntu glibc · x64 · go 1.26 · go 1

package-level total, not an API

0 of 7 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed

Project observations
34 / 41
Contract verifications
0 / 7
Usage records
34
Independent reporting peers
3
Last recorded
2026-09-14

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 0

First observed break

v0.21.1

linux · go@1.26

5 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:c2ae6d87252c4f443f14d40584c4012a25213fbf0bb7b5e35604e6d35d608229

Library Version Health Measured there Projects
github.com/google/go-cmp v0.7.0 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
golang.org/x/sync v0.21.0 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
golang.org/x/sync v0.22.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
golang.org/x/sys v0.47.0 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
golang.org/x/sys v0.48.0 CANDIDATE Correlated change; unproven combination 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.

Moved: 3 · 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