CodeSampleX

Recordsgolanggolang.org/x/modfailure issue

Failure signature

PROJECT_COMPILE exit 1 ×2

<path> <str> imported and not used

Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-09-06 · Last seen: 2026-10-09

sha256:964ddac6b19a…

golang.org/x/mod/module.InvalidVersionError golang.org/x/mod/module.ModuleError golang.org/x/mod/module.Version golang.org/x/mod/module.VersionError

Where it was measured

PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

Where it reproduced

Nearest known PASS/FAIL boundaries

The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.

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.

Libraryv0.40.0v0.39.0v0.38.0v0.37.0v0.24.0v0.8.0v0.6.0-dev.0.20220419223038-86c51ed26bb4v0.6.0-dev.0.20220106191415-9b9b3d81d5e3v0.1.1-0.20191105210325-c90efee705ee
golang.org/x/crypto — — — — — — v0.3.0 — v0.0.0-20210711020723-a769d52b0f97
golang.org/x/tools — v0.49.0 v0.48.0 v0.46.0 v0.31.0 v0.1.12 v0.1.12 — —
golang.org/x/xerrors — — — — — — — — v0.0.0-20200804184101-5ec99f83aff1

Moved: 2 · unchanged at every release: 1

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

Published answers for the affected releases

Back to the package