Recordsgolanggolang.org/x/cryptov0.0.0-20200622213623-75b288015ac9blake2b.Sum256
Change the conditions
Current conditions
blake2b.Sum256 @v0.0.0-20200622213623-75b288015ac9debian glibc · x64 · go 1.26 · go · go
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 1 / 1
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-17
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 24. 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 | 3 project-days |
| golang.org/x/net | v0.0.0-20190813141303-74dc4d7220e7 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| golang.org/x/net | v0.0.0-20200625001655-4c5254603344 | CHANGED Version changed, no linked failure | contract passed | 23 project-days |
| golang.org/x/net | v0.0.0-20200707034311-ab3426394381 | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| golang.org/x/net | v0.0.0-20200822124328-c89045814202 | CHANGED Version changed, no linked failure | contract passed | 29 project-days |
| golang.org/x/net | v0.0.0-20201021035429-f5854403a974 | CHANGED Version changed, no linked failure | contract passed | 48 project-days |
| golang.org/x/net | v0.0.0-20201110031124-69a78807bb2b | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| golang.org/x/net | v0.0.0-20201209123823-ac852fbbde11 | CHANGED Version changed, no linked failure | contract passed | 6 project-days |
| golang.org/x/net | v0.0.0-20210119194325-5f4716e94777 | CHANGED Version changed, no linked failure | contract passed | 9 project-days |
| golang.org/x/net | v0.0.0-20210405180319-a5a99cb37ef4 | CHANGED Version changed, no linked failure | contract passed | 8 project-days |
| golang.org/x/net | v0.0.0-20210503060351-7fd8e65b6420 | CHANGED Version changed, no linked failure | contract passed | 13 project-days |
| golang.org/x/net | v0.0.0-20210525063256-abc453219eb5 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| golang.org/x/sys | v0.0.0-20190412213103-97732733099d | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| golang.org/x/sys | v0.0.0-20190813064441-fde4db37ae7a | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| golang.org/x/sys | v0.0.0-20200323222414-85ca7c5b95cd | CHANGED Version changed, no linked failure | contract passed | 24 project-days |
| golang.org/x/sys | v0.0.0-20200625212154-ddb9806d33ae | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| golang.org/x/sys | v0.0.0-20200803210538-64077c9b5642 | CHANGED Version changed, no linked failure | nothing measured | 14 project-days |
| golang.org/x/sys | v0.0.0-20200930185726-fdedc70b468f | CHANGED Version changed, no linked failure | nothing measured | 49 project-days |
| golang.org/x/sys | v0.0.0-20210104204734-6f8348627aad | CHANGED Version changed, no linked failure | contract passed | 6 project-days |
| golang.org/x/sys | v0.0.0-20210124154548-22da62e12c0c | CHANGED Version changed, no linked failure | contract passed | 8 project-days |
| golang.org/x/sys | v0.0.0-20210510120138-977fb7262007 | CHANGED Version changed, no linked failure | contract passed | 8 project-days |
| golang.org/x/sys | v0.0.0-20210603081109-ebe580a85c40 | CHANGED Version changed, no linked failure | contract passed | 11 project-days |
| golang.org/x/sys | v0.0.0-20210806184541-e5e7981a1069 | CHANGED Version changed, no linked failure | contract passed | 12 project-days |
| golang.org/x/sys | v0.47.0 | CHANGED Version changed, no linked failure | contract passed | 2 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.