CodeSampleX

Recordsgolanggolang.org/x/modv0.39.0

Change the conditions
Fixed
OSlinux Package versionv0.39.0
Filter Runtimego 1.26 Symbolwhole package Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

golang.org/x/mod @v0.39.0linux · glibc · x64 · go 1.26 · go · go

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-02

Dependency Health

Observed combinations and failure evidence for this release

Changed 1 · Steady 0

Dependency changes observed: 1. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
golang.org/x/tools v0.49.0 CHANGED Version changed, no linked failure contract passed 3 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.

Libraryv0.39.0v0.38.0v0.37.0v0.35.0v0.24.0v0.18.0v0.13.0v0.8.0v0.6.0-dev.0.20220419223038-86c51ed26bb4v0.3.0v0.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.49.0 v0.48.0 v0.47.0 v0.44.0 v0.13.0 v0.22.0 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.