Recordsgolanggolang.org/x/cryptofailure issue
Failure signature
PROJECT_RESOLVE exit 1 ×1
main.go:<n>:<n>: missing go.sum entry for module providing package golang.org/x/crypto/bcrypt (imported by example.com/sample); to add:
Evidence quality: complete · go/module · resolve-diagnostic · outer go run · First recorded: 2026-10-10 · Last seen: 2026-10-10
sha256:ece2faa602ca…
golang.org/x/crypto/bcrypt.CompareHashAndPassword golang.org/x/crypto/bcrypt.Cost golang.org/x/crypto/bcrypt.DefaultCost golang.org/x/crypto/bcrypt.GenerateFromPassword golang.org/x/crypto/bcrypt.MaxCost golang.org/x/crypto/bcrypt.MinCost
Where it was measured
PASS means the release recorded a passing observation at PROJECT_RESOLVE 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-20190820162420-60c769a6c586 not measured
- v0.0.0-20190701094942-4def268fd1a4 not measured
- v0.0.0-20190605123033-f99c8df09eb5 not measured
- v0.0.0-20190510104115-cbcb75029529 FAIL
- v0.0.0-20190426145343-a29dc8fdc734 not measured
- v0.0.0-20190411191339-88737f569e3a not measured
- v0.0.0-20190313024323-a1f597ede03a not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-10-10 → 2026-10-10
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.0.0-20190820162420-60c769a6c586 | v0.0.0-20190701094942-4def268fd1a4 | v0.0.0-20190605123033-f99c8df09eb5 | v0.0.0-20190510104115-cbcb75029529 | v0.0.0-20190426145343-a29dc8fdc734 | v0.0.0-20190411191339-88737f569e3a | v0.0.0-20190313024323-a1f597ede03a |
|---|---|---|---|---|---|---|---|
| golang.org/x/net | v0.0.0-20190813141303-74dc4d7220e7 | v0.0.0-20190404232315-eb5bcb51f2a3 | v0.0.0-20190404232315-eb5bcb51f2a3 | v0.0.0-20190620200207-3b0461eec859 | v0.0.0-20190620200207-3b0461eec859 | — | — |
| golang.org/x/sys | v0.0.0-20220722155257-8c9f86f7a55f | v0.0.0-20190726091711-fc99dfbffb4e | v0.0.0-20190412213103-97732733099d | v0.0.0-20190412213103-97732733099d | v0.0.0-20190412213103-97732733099d | v0.0.0-20190403152447-81d4e9dc473e | v0.0.0-20190316082340-a2f829d7f35f |
Moved: 2 · 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
- No release in this window recorded a passing observation at PROJECT_RESOLVE.
- Releases in this window never measured at PROJECT_RESOLVE: 6
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/crypto v0.0.0-20190510104115-cbcb75029529: bcrypt.Cost 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.Costgo 1.26.6 MIT-0 · 2026-10-10
- golang.org/x/crypto v0.0.0-20190510104115-cbcb75029529: bcrypt.MinCost 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.MinCostgo 1.26.6 MIT-0 · 2026-10-10
- golang.org/x/crypto v0.0.0-20190510104115-cbcb75029529: 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. HOWgolang.org/x/crypto/bcrypt.GenerateFromPassword MIT-0 · 2026-10-10