Recordsgolanggolang.org/x/cryptofailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
stat main.go: no such file or directory
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:138a106a5937…
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.0.0-20210921155107-089bfa567519 not measured
- v0.0.0-20210711020723-a769d52b0f97 not measured
- v0.0.0-20210616213533-5ff15b29337e not measured
- v0.0.0-20210322153248-0c34fe9e7dc2 FAIL
- v0.0.0-20201203163018-be400aefbc4c not measured
- v0.0.0-20201002170205-7f63de1d35b0 not measured
- v0.0.0-20200622213623-75b288015ac9 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×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.0.0-20210921155107-089bfa567519 | v0.0.0-20210711020723-a769d52b0f97 | v0.0.0-20210616213533-5ff15b29337e | v0.0.0-20210322153248-0c34fe9e7dc2 | v0.0.0-20201203163018-be400aefbc4c | v0.0.0-20201002170205-7f63de1d35b0 | v0.0.0-20200622213623-75b288015ac9 |
|---|---|---|---|---|---|---|---|
| golang.org/x/net | v0.4.0 | v0.0.0-20210226172049-e18ecbb05110 | v0.0.0-20210226172049-e18ecbb05110 | v0.0.0-20210226172049-e18ecbb05110 | v0.0.0-20190813141303-74dc4d7220e7 | v0.0.0-20210503060351-7fd8e65b6420 | v0.0.0-20201110031124-69a78807bb2b |
| golang.org/x/sys | v0.47.0 | v0.0.0-20210615035016-665e8c7367d1 | v0.0.0-20210615035016-665e8c7367d1 | v0.0.0-20201119102817-f84b799fce68 | v0.0.0-20191026070338-33540a1f6037 | v0.0.0-20210806184541-e5e7981a1069 | v0.0.0-20200930185726-fdedc70b468f |
| golang.org/x/term | — | v0.0.0-20201126162022-7de9c90e9dd1 | v0.0.0-20201126162022-7de9c90e9dd1 | v0.0.0-20201126162022-7de9c90e9dd1 | v0.0.0-20201117132131-f5c789dd3221 | — | — |
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: 6
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.