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

Where it was measured

PASS means the release recorded a passing observation at UNKNOWN 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-20210616213533-5ff15b29337e not measured
• v0.0.0-20210322153248-0c34fe9e7dc2 not measured
• v0.0.0-20201203163018-be400aefbc4c not measured
• v0.0.0-20201002170205-7f63de1d35b0 FAIL
• v0.0.0-20200622213623-75b288015ac9 not measured
• v0.0.0-20191011191535-87dc89f01550 not measured
• v0.0.0-20190820162420-60c769a6c586 FAIL
• v0.0.0-20190605123033-f99c8df09eb5 not measured
• v0.0.0-20190510104115-cbcb75029529 not measured

Where it reproduced

• os=linux · runtime=go@1.26 ×2 2026-10-20 → 2026-10-23

Nearest known PASS/FAIL boundaries

No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.

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

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• The captured output could not establish: stage-unknown.
• No release in this window recorded a passing observation at UNKNOWN.
• Releases in this window never measured at UNKNOWN: 7
• No failure domain was inferred for this failure.

Published answers for the affected releases

No published sample names these releases.