CodeSampleX

Recordsgolanggoogle.golang.org/protobufv1.36.6

Change the conditions
Fixed
OSdebian glibc Package versionv1.36.6
Filter Runtimego 1.26 Symbolwhole package Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

google.golang.org/protobuf @v1.36.6debian 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
12
Independent reporting peers
1
Last recorded
2026-10-21

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 0

First observed break

v1.36.6

linux · go@1.26

6 FAIL · stage: UNKNOWN · fingerprint: sha256:042f6e977a16262a7e633b3137ce9291be598b66496d9201e447ee2b8efa6eb8

Library Version Health Measured there Projects
github.com/golang/protobuf v1.5.0 CANDIDATE Correlated change; unproven combination 56 project-days
github.com/golang/protobuf v1.5.4 CANDIDATE Correlated change; unproven combination 7 project-days
github.com/google/go-cmp v0.5.5 CANDIDATE Correlated change; unproven combination 22 project-days
github.com/google/go-cmp v0.5.9 CANDIDATE Correlated change; unproven combination 34 project-days
github.com/google/go-cmp v0.7.0 CANDIDATE Correlated change; unproven combination 7 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.

Libraryv1.36.12v1.36.11v1.36.10v1.36.6v1.36.5v1.36.4v1.35.2v1.35.1v1.34.2v1.34.1v1.33.0v1.32.0v1.31.0v1.30.0v1.28.0v1.27.1v1.26.0v1.26.0-rc.1v1.25.0v1.24.0v1.23.1-0.20200526195155-81db48ad09ccv1.23.0v1.22.0v1.21.0
github.com/golang/protobuf v1.5.2 v1.5.3 v1.5.3 v1.5.4 v1.5.4 v1.5.3 v1.5.0 v1.5.4 v1.5.3 v1.5.4 v1.5.2 v1.5.0 v1.5.3 v1.5.3 v1.5.3 v1.5.2 v1.5.3 — v1.4.1 v1.4.2 v1.4.0 v1.4.3 v1.4.1 v1.4.0
github.com/google/go-cmp v0.7.0 v0.7.0 v0.7.0 v0.7.0 v0.6.0 v0.5.5 v0.6.0 v0.6.0 v0.5.9 v0.6.0 v0.6.0 v0.5.5 v0.5.9 v0.5.9 v0.6.0 v0.5.5 v0.5.5 v0.5.5 v0.5.4 v0.4.1 v0.4.0 v0.4.0 v0.4.0 v0.4.0
google.golang.org/genproto — — — — — — — — — — — — — — — — — — v0.0.0-20200729003335-053ba62fc06f v0.0.0-20200618031413-b414f8b61790 — — — —

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