CodeSampleX

Recordsgolanggolang.org/x/crypto

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
OSubuntu glibc Package versionv0.20.0 Architecturex64
Filter Runtimego 1.26 Package managergo 1 Clear filters
libc × Symbol
32026-08-31

The cube reads the newest 6 versions and the first 10 symbols of each, so an empty cell here can mean "outside that window" rather than "never measured".

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

Observed problems 3 · Steady 0

First observed break

v0.20.0 golang.org/x/net@v0.21.0

linux

13 FAIL · stage: PROJECT_PROCESS

Library Version Health Measured there Projects
golang.org/x/net v0.21.0 FAIL Linked failure observed; version changed across releases contract passed 6 project-days
golang.org/x/sys v0.17.0 FAIL Linked failure observed; version changed across releases contract passed 6 project-days
golang.org/x/term v0.17.0 FAIL Linked failure observed; version changed across releases builds observed 6 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.55.0v0.54.0v0.52.0v0.50.0v0.48.0v0.36.0v0.20.0v0.19.0v0.0.0-20210921155107-089bfa567519v0.0.0-20200622213623-75b288015ac9
golang.org/x/net v0.57.0 v0.57.0 v0.55.0 v0.53.0 v0.50.0 v0.21.0 v0.21.0 v0.21.0 v0.4.0 v0.0.0-20210525063256-abc453219eb5
golang.org/x/sys v0.47.0 v0.47.0 v0.45.0 v0.43.0 v0.41.0 v0.31.0 v0.17.0 v0.17.0 v0.47.0 v0.47.0
golang.org/x/term v0.45.0 v0.45.0 v0.43.0 v0.42.0 v0.40.0 v0.30.0 v0.17.0 v0.17.0

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.