CodeSampleX

Recordsgolanggithub.com/prometheus/procfsv0.6.0github.com/prometheus/procfs.FS.Meminfo

Change the conditions
Fixed
Package versionv0.6.0 Symbolgithub.com/prometheus/procfs.FS.Meminfo
Filter OSdebian glibc Runtimego 1.26 Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

github.com/prometheus/procfs.FS.Meminfo @v0.6.0debian 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
1 / 1
Contract verifications
2 / 2
Independent reporting peers
1
Last recorded
2026-09-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 6 · Steady 0

First observed break

v0.6.0

linux

3 FAIL · stage: UNKNOWN · fingerprint: sha256:9922ca80f240bbcc7904b679943bbc3e6a9f08fa3dc0e823aadcc4450e6a4830

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/google/go-cmp v0.5.4 CANDIDATE Correlated change; unproven combination contract passed 10 project-days
github.com/google/go-cmp v0.5.5 CANDIDATE Correlated change; unproven combination contract passed 12 project-days
golang.org/x/sync v0.0.0-20201207232520-09787c993a3a CANDIDATE Correlated change; unproven combination nothing measured 22 project-days
golang.org/x/sys v0.0.0-20210124154548-22da62e12c0c CANDIDATE Correlated change; unproven combination builds observed 9 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

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.22.0v0.21.1v0.20.1v0.12.0v0.7.3v0.6.0v0.1.3
github.com/google/go-cmp v0.7.0 v0.7.0 v0.7.0 v0.5.9 v0.5.5 v0.5.4 v0.4.0
golang.org/x/sync v0.22.0 v0.22.0 v0.20.0 v0.12.0 v0.0.0-20201207232520-09787c993a3a v0.0.0-20201207232520-09787c993a3a v0.0.0-20190911185100-cd5d95a43a6e
golang.org/x/sys v0.47.0 v0.48.0 v0.45.0 v0.31.0 v0.0.0-20220114195835-da31bd327af9 v0.47.0 v0.0.0-20200625212154-ddb9806d33ae

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