CodeSampleX

Recordsgolanggoogle.golang.org/genproto/googleapis/rpc

Compatibility cube

Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.

Fixed
Package versionv0.0.0-20260904194346-d0f1323225a4
Filter Runtimego 1.26 Architecturex64 Execution contextgo libcglibc Clear filters
How to read the grid

Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.

  • no sample at this coordinate yet
  • there is a sample here, and nothing of ours has run it at this coordinate yet
  • there is a sample here, and our run of it at this coordinate came back clean
  • there is a sample here, and our run of it at this coordinate failed
  • there is a sample here, and this coordinate records both a passing and a failing run of it
  • nothing recorded — unknown, never "works" and never "broken"
  • there is a level below this cell — click to open it

A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.

Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.

Dependency Health

Observed combinations and failure evidence for this release

Changed 1 · Steady 0

Dependency changes observed: 1. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
google.golang.org/protobuf v1.36.12 CHANGED Version changed, no linked failure contract passed 17 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.

Libraryv0.0.0-20260904194346-d0f1323225a4v0.0.0-20260831171406-18b4a7587f8av0.0.0-20260825221802-da73d73af1c5v0.0.0-20260819154853-08b0e4226688v0.0.0-20260526163538-3dc84a4a5aaav0.0.0-20260427160629-7cedc36a6bc4v0.0.0-20260406210006-6f92a3bedf2dv0.0.0-20260401024825-9d38bb4040a9v0.0.0-20250728155136-f173205681a0v0.0.0-20250707201910-8d1bb00bc6a7v0.0.0-20250218202821-56aae31c358av0.0.0-20250115164207-1a7da9e5054fv0.0.0-20241007155032-5fefd90f89a9v0.0.0-20240826202546-f6391c0de4c7v0.0.0-20240814211410-ddb44dafa142v0.0.0-20230711160842-782d3b101e98
google.golang.org/protobuf v1.36.12 v1.36.12 v1.36.12 v1.36.12 v1.36.11 v1.36.12 v1.36.11 v1.36.11 v1.36.12 v1.36.6 v1.36.5 v1.36.5 v1.35.1 v1.34.2 v1.34.2 v1.31.0
google.golang.org/genproto — — — — — — — — — — — — — — — v0.0.0-20230711160842-782d3b101e98

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.