CodeSampleX

Recordsgolanggolang.org/x/modfailure issue

Failure signature

UNKNOWN exit 1 Evidence gap ×1

FAIL: module.EscapeVersion expected error on invalid semver · exit status 1

Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-08-31 · Last seen: 2026-08-31

sha256:289e86916f87…

golang.org/x/mod/module.Check golang.org/x/mod/module.CheckPath golang.org/x/mod/module.EscapePath golang.org/x/mod/module.EscapeVersion golang.org/x/mod/module.MatchPathMajor golang.org/x/mod/module.Sort golang.org/x/mod/module.SplitPathVersion golang.org/x/mod/module.Version

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.

Where it reproduced

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.

Libraryv0.24.0v0.18.0v0.13.0
golang.org/x/tools v0.31.0 v0.22.0 v0.14.0

Moved: 1 · 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

Published answers for the affected releases

Back to the package