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.
Showing the environments with the most evidence. 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
Dependency changes observed: 19. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/net | v0.0.0-20190404232315-eb5bcb51f2a3 | CHANGED Version changed, no linked failure | contract passed | 7 project-days |
| golang.org/x/net | v0.0.0-20190620200207-3b0461eec859 | CHANGED Version changed, no linked failure | contract passed | 18 project-days |
| golang.org/x/net | v0.0.0-20190813141303-74dc4d7220e7 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| golang.org/x/net | v0.0.0-20191209160850-c0dbc17a3553 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| golang.org/x/net | v0.0.0-20200114155413-6afb5195e5aa | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| golang.org/x/net | v0.0.0-20200202094626-16171245cfb2 | CHANGED Version changed, no linked failure | contract passed | 7 project-days |
| golang.org/x/net | v0.0.0-20200226121028-0de0cce0169b | CHANGED Version changed, no linked failure | nothing measured | 2 project-days |
| golang.org/x/net | v0.0.0-20200324143707-d3edc9973b7e | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| golang.org/x/net | v0.0.0-20200520182314-0ba52f642ac2 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| golang.org/x/net | v0.0.0-20210405180319-a5a99cb37ef4 | CHANGED Version changed, no linked failure | contract passed | 15 project-days |
| golang.org/x/sys | v0.0.0-20190412213103-97732733099d | CHANGED Version changed, no linked failure | contract passed | 21 project-days |
| golang.org/x/sys | v0.0.0-20191001151750-bb3f8db39f24 | CHANGED Version changed, no linked failure | nothing measured | 6 project-days |
| golang.org/x/sys | v0.0.0-20191228213918-04cbcbbfeed8 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| golang.org/x/sys | v0.0.0-20200122134326-e047566fdf82 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| golang.org/x/sys | v0.0.0-20200202164722-d101bd2416d5 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| golang.org/x/sys | v0.0.0-20200212091648-12a6c2dcc1e4 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| golang.org/x/sys | v0.0.0-20200331124033-c3d80250170d | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| golang.org/x/sys | v0.0.0-20200523222454-059865788121 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| golang.org/x/sys | v0.0.0-20210510120138-977fb7262007 | CHANGED Version changed, no linked failure | contract passed | 15 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.
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.