CodeSampleX

Recordsgolanggolang.org/x/cryptofailure issue

Failure signature

UNKNOWN exit 1 Evidence gap ×1

panic: runtime error: integer divide by zero · goroutine 1 [running]: …

Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-08-31 · Last seen: 2026-08-31

sha256:caa314254be0…

golang.org/x/crypto/scrypt.Key

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.26.0v0.25.0v0.23.0v0.22.0v0.21.0v0.20.0v0.19.0
golang.org/x/net — v0.21.0 — v0.24.0 v0.23.0 v0.21.0 v0.21.0
golang.org/x/sys — v0.22.0 — — v0.18.0 v0.17.0 v0.17.0
golang.org/x/term — v0.22.0 — — v0.18.0 v0.17.0 v0.17.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