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
Package versionv0.0.0-20200622213623-75b288015ac9

No recorded evidence matches these filters. Nothing is inferred; clear a filter to widen the slice.

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".

Dependency Health

Observed combinations and failure evidence for this release

Changed 4 · Steady 0

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

Library Version Health Measured there Projects
golang.org/x/net v0.0.0-20200625001655-4c5254603344 CHANGED Version changed, no linked failure builds observed 11 project-days
golang.org/x/net v0.0.0-20210525063256-abc453219eb5 CHANGED Version changed, no linked failure builds observed 2 project-days
golang.org/x/sys v0.0.0-20210603081109-ebe580a85c40 CHANGED Version changed, no linked failure builds observed 11 project-days
golang.org/x/sys v0.47.0 CHANGED Version changed, no linked failure 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.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.