Records/golang/golang.org/x/crypto/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• v0.0.0-20210921155107-089bfa567519 not measured
• v0.0.0-20210711020723-a769d52b0f97 PASS 1 passing observations
• v0.0.0-20210616213533-5ff15b29337e PASS 3 passing observations
• v0.0.0-20210322153248-0c34fe9e7dc2 FAIL
• v0.0.0-20201203163018-be400aefbc4c PASS 3 passing observations
• v0.0.0-20201002170205-7f63de1d35b0 PASS 4 passing observations
• v0.0.0-20200622213623-75b288015ac9 not measured

Where it reproduced

• os=linux · runtime=go@1.26 ×1 2026-09-04 → 2026-09-04

Nearest known PASS/FAIL boundaries

The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.

• Last passing release v0.0.0-20201203163018-be400aefbc4c → first failing release v0.0.0-20210322153248-0c34fe9e7dc2

  What differs across the boundary

  • golang.org/x/net v0.0.0-20190404232315-eb5bcb51f2a3, v0.0.0-20190813141303-74dc4d7220e7 → v0.0.0-20210226172049-e18ecbb05110 hypothesis
  • golang.org/x/sys v0.0.0-20191026070338-33540a1f6037 → v0.0.0-20201119102817-f84b799fce68 hypothesis
  • golang.org/x/term v0.0.0-20201117132131-f5c789dd3221 → v0.0.0-20201126162022-7de9c90e9dd1 hypothesis

  A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.

• Last failing release v0.0.0-20210322153248-0c34fe9e7dc2 → first passing release v0.0.0-20210616213533-5ff15b29337e

  What differs across the boundary

  • golang.org/x/sys v0.0.0-20210615035016-665e8c7367d1 → v0.0.0-20201119102817-f84b799fce68 hypothesis

  A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.

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.

Evidence gaps

• Releases in this window never measured at PROJECT_COMPILE: 2
• No failure domain was inferred for this failure.

Published answers for the affected releases

No published sample names these releases.