CodeSampleX

Recordsgolanggolang.org/x/cryptofailure issue

Failure signature

UNKNOWN exit 1 Evidence gap ×5

go: <path> already exists

Evidence quality: complete · go · unclassified-diagnostic · outer go mod · gap stage-unknown · First recorded: 2026-08-29 · Last seen: 2026-09-04

sha256:9922ca80f240…

golang.org/x/crypto/bcrypt.CompareHashAndPassword golang.org/x/crypto/bcrypt.Cost golang.org/x/crypto/bcrypt.DefaultCost golang.org/x/crypto/bcrypt.ErrMismatchedHashAndPassword golang.org/x/crypto/bcrypt.GenerateFromPassword golang.org/x/crypto/bcrypt.MinCost

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.

Where it reproduced

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.

Libraryv0.56.0v0.55.0v0.54.0v0.31.0v0.27.0v0.26.0v0.3.0v0.0.0-20220331220935-ae2d96664a29v0.0.0-20210921155107-089bfa567519
golang.org/x/net v0.57.0 v0.57.0 v0.57.0 v0.21.0 v0.21.0 — v0.2.0 — v0.4.0
golang.org/x/sys v0.47.0 v0.47.0 v0.47.0 v0.28.0 v0.25.0 — v0.2.0 — v0.47.0
golang.org/x/term v0.45.0 v0.45.0 v0.45.0 v0.27.0 v0.24.0 — v0.2.0 — —

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

Published answers for the affected releases

Back to the package