Recordsgolanggolang.org/x/modfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×2
node:internal/modules/cjs/loader:<n> · const err = new Error(message); · ^ · Error: Cannot find module <str>
Evidence quality: complete · node · unclassified-diagnostic · outer node · gap stage-unknown · First recorded: 2026-08-29 · Last seen: 2026-08-30
sha256:8310a83be884…
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.13.0 not measured
- v0.8.0 not measured
- v0.6.0-dev.0.20220419223038-86c51ed26bb4 not measured
- v0.6.0-dev.0.20220106191415-9b9b3d81d5e3 FAIL
- v0.4.2 not measured
- v0.3.0 not measured
- v0.1.1-0.20191105210325-c90efee705ee not measured
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×2 2026-08-29 → 2026-08-30
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.13.0 | v0.8.0 | v0.6.0-dev.0.20220419223038-86c51ed26bb4 | v0.6.0-dev.0.20220106191415-9b9b3d81d5e3 | v0.3.0 | v0.1.1-0.20191105210325-c90efee705ee |
|---|---|---|---|---|---|---|
| golang.org/x/crypto | — | — | v0.3.0 | — | v0.0.0-20200622213623-75b288015ac9 | v0.0.0-20191011191535-87dc89f01550 |
| golang.org/x/tools | v0.14.0 | v0.6.0 | v0.1.12 | — | v0.0.0-20200825202427-b303f430e36d | — |
| golang.org/x/xerrors | — | — | — | — | v0.0.0-20200804184101-5ec99f83aff1 | v0.0.0-20191011141410-1b5146add898 |
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
- golang.org/x/mod v0.6.0-dev.0.20220106191415-9b9b3d81d5e3: module.Check 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. HOWmodule.Check MIT-0 · 2026-08-27