CodeSampleX

Recordsgolanggolang.org/x/modv0.37.0golang.org/x/mod/module.EscapePath

Change the conditions
Fixed
Runtimego (version not recorded) Symbolgolang.org/x/mod/module.EscapePath
Filter OSwindows 11 Package versionv0.37.0 Architecturex64 Package managergo Clear filters

Current conditions

golang.org/x/mod/module.EscapePath @v0.37.0windows 11 · x64 · go (version not recorded) · go

1 of 1 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
1 / 1
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-13

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

v0.37.0

go@1.26

6 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
golang.org/x/tools v0.46.0 CANDIDATE Correlated change; unproven combination builds observed 3 project-days
golang.org/x/tools v0.47.0 CANDIDATE Correlated change; unproven combination builds observed 12 project-days

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

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.

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.

Recent failure clusters