Recordsgolanggolang.org/x/cryptofailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×3
<path>: No module named pip
Evidence quality: complete · python3 · unclassified-diagnostic · outer python3 · gap stage-unknown · First recorded: 2026-08-30 · Last seen: 2026-08-31
sha256:72ba2d1e946f…
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.41.0 not measured
- v0.37.0 not measured
- v0.36.0 FAIL
- v0.33.0 not measured
- v0.31.0 not measured
- v0.11.1-0.20230711161743-2e82bdd1719d not measured
- v0.3.0 not measured
- v0.0.0-20220331220935-ae2d96664a29 FAIL
- v0.0.0-20210921155107-089bfa567519 not measured
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×3 2026-08-30 → 2026-08-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.37.0 | v0.36.0 | v0.33.0 | v0.31.0 | v0.11.1-0.20230711161743-2e82bdd1719d | v0.3.0 | v0.0.0-20220331220935-ae2d96664a29 | v0.0.0-20210921155107-089bfa567519 |
|---|---|---|---|---|---|---|---|---|
| golang.org/x/net | v0.21.0 | v0.21.0 | v0.21.0 | v0.21.0 | v0.10.0 | v0.2.0 | — | v0.4.0 |
| golang.org/x/sys | v0.32.0 | v0.31.0 | v0.30.0 | v0.28.0 | v0.47.0 | v0.2.0 | — | v0.47.0 |
| golang.org/x/term | v0.31.0 | v0.30.0 | v0.29.0 | v0.27.0 | v0.10.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
- 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: 7
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/crypto v0.36.0: scrypt.Key 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. HOWscrypt.Key MIT-0 · 2026-09-02
- golang.org/x/crypto v0.36.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. HOWgolang.org/x/crypto/bcrypt.CompareHashAndPasswordgolang.org/x/crypto/bcrypt.Costgolang.org/x/crypto/bcrypt.GenerateFromPassword MIT-0 · 2026-08-27
- golang.org/x/crypto v0.36.0: chacha20poly1305.NewX 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. HOWchacha20poly1305.NewXgo 1.26.6 MIT-0 · 2026-08-26
- golang.org/x/crypto v0.0.0-20220331220935-ae2d96664a29: 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-08-27