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

Where it was measured

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

• v0.11.1-0.20230711161743-2e82bdd1719d PASS 8 passing observations
• v0.3.0 PASS 25 passing observations
• v0.0.0-20220525230936-793ad666bf5e PASS 41 passing observations
• v0.0.0-20220331220935-ae2d96664a29 FAIL
• v0.0.0-20210921155107-089bfa567519 not measured
• v0.0.0-20210711020723-a769d52b0f97 PASS 28 passing observations
• v0.0.0-20210616213533-5ff15b29337e PASS 22 passing observations

Where it reproduced

• executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-08-29 → 2026-08-29

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-20210711020723-a769d52b0f97 → first failing release v0.0.0-20220331220935-ae2d96664a29

  Releases between them never measured at this stage: 1

  What differs across the boundary

  • golang.org/x/net v0.0.0-20210226172049-e18ecbb05110 → — hypothesis
  • golang.org/x/sys v0.0.0-20210615035016-665e8c7367d1 → — hypothesis
  • golang.org/x/term 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-20220331220935-ae2d96664a29 → first passing release v0.0.0-20220525230936-793ad666bf5e

  What differs across the boundary

  • golang.org/x/net v0.0.0-20211112202133-69e39bad7dc2 → — hypothesis
  • golang.org/x/sys v0.0.0-20210615035016-665e8c7367d1, v0.0.0-20220608164250-635b8c9b7f68, v0.8.0, v0.9.0 → — hypothesis
  • golang.org/x/term 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.

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_PROCESS: 1
• No failure domain was inferred for this failure.

Published answers for the affected releases

• golang.org/x/crypto v0.0.0-20220331220935-ae2d96664a29: bcrypt.CompareHashAndPassword, bcrypt.Cost, bcrypt.GenerateFromPassword Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWbcrypt.CompareHashAndPasswordbcrypt.Costbcrypt.GenerateFromPassword MIT-0 · 2026-08-27