Recordsgolanggolang.org/x/cryptofailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×7
doc: cannot find package <str> in any of: · ($GOROOT not set) · <path> (from $GOPATH)
Evidence quality: complete · go · unclassified-diagnostic · outer go · gap stage-unknown · First recorded: 2026-09-04 · Last seen: 2026-10-31
sha256:3b3190f2cd44…
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.50.0 not measured
- v0.49.0 FAIL
- v0.48.0 FAIL
- v0.47.0 not measured
- v0.43.0 FAIL
- v0.42.0 not measured
- v0.0.0-20220525230936-793ad666bf5e FAIL
- v0.0.0-20210711020723-a769d52b0f97 FAIL
- v0.0.0-20190701094942-4def268fd1a4 FAIL
Where it reproduced
- os=linux · runtime=go@1.26 ×7 2026-09-04 → 2026-10-31
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.
| Library | v0.50.0 | v0.49.0 | v0.48.0 | v0.47.0 | v0.43.0 | v0.42.0 | v0.0.0-20220525230936-793ad666bf5e | v0.0.0-20210711020723-a769d52b0f97 | v0.0.0-20190701094942-4def268fd1a4 |
|---|---|---|---|---|---|---|---|---|---|
| golang.org/x/net | v0.53.0 | v0.51.0 | v0.50.0 | v0.58.0 | v0.46.0 | v0.43.0 | v0.0.0-20211112202133-69e39bad7dc2 | v0.0.0-20210226172049-e18ecbb05110 | v0.0.0-20190404232315-eb5bcb51f2a3 |
| golang.org/x/sys | v0.44.0 | v0.42.0 | v0.47.0 | v0.47.0 | v0.37.0 | v0.36.0 | v0.0.0-20220608164250-635b8c9b7f68 | v0.0.0-20210615035016-665e8c7367d1 | v0.0.0-20190726091711-fc99dfbffb4e |
| golang.org/x/term | v0.42.0 | v0.41.0 | v0.40.0 | v0.39.0 | v0.36.0 | v0.35.0 | v0.0.0-20201126162022-7de9c90e9dd1 | v0.0.0-20201126162022-7de9c90e9dd1 | — |
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: 3
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/crypto v0.49.0: bcrypt.CompareHashAndPassword, bcrypt.Cost, bcrypt.GenerateFromPassword 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-10-10
- golang.org/x/crypto v0.48.0: sha3.NewShake256 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. HOWgolang.org/x/crypto/sha3.NewShake256 MIT-0 · 2026-09-04
- golang.org/x/crypto v0.48.0: sha3.New256 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. HOWgolang.org/x/crypto/sha3.New256 MIT-0 · 2026-09-04
- golang.org/x/crypto v0.48.0: bcrypt.ErrHashTooShort 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. HOWgolang.org/x/crypto/bcrypt.ErrHashTooShort MIT-0 · 2026-09-04