Recordsgolanggolang.org/x/cryptofailure issue
Failure signature
PROCESS_START process start failed Evidence gap ×1
Evidence quality: partial · pytest · structured-termination · outer pytest · gap diagnostic-missing · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:2617e70290c8…
Where it was measured
PASS means the release recorded a passing observation at PROCESS_START and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v0.42.0 not measured
- 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.27.0 not measured
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-08-31 → 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.42.0 | v0.37.0 | v0.36.0 | v0.33.0 | v0.31.0 | v0.27.0 |
|---|---|---|---|---|---|---|
| golang.org/x/net | v0.43.0 | v0.21.0 | v0.21.0 | v0.21.0 | v0.21.0 | v0.21.0 |
| golang.org/x/sys | v0.36.0 | v0.32.0 | v0.31.0 | v0.30.0 | v0.28.0 | v0.25.0 |
| golang.org/x/term | v0.35.0 | v0.31.0 | v0.30.0 | v0.29.0 | v0.27.0 | v0.24.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: diagnostic-missing.
- No release in this window recorded a passing observation at PROCESS_START.
- Releases in this window never measured at PROCESS_START: 6
- 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