CodeSampleX

Recordsgolanggolang.org/x/modv0.4.2

Change the conditions
Fixed
Package versionv0.4.2 Package managergo 1
Filter OSubuntu glibc Runtimego 1.26 Symbolwhole package Architecturex64 libcglibc Clear filters

Current conditions

golang.org/x/mod @v0.4.2ubuntu glibc · x64 · go 1.26 · go 1

package-level total, not an API

1 of 2 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
1 / 2
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-30
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 0

First observed break

v0.4.2

linux · go@1.26

1 FAIL · stage: PROJECT_TEST · fingerprint: sha256:36a7340bb4effa7c61df77651c37960b82a822df3ee9bb6e3d125c70e06e95b1

View exact conditions View failure cluster
Library Version Health Measured there Projects
golang.org/x/crypto v0.0.0-20191011191535-87dc89f01550 CANDIDATE Correlated change; unproven combination builds observed 1 project-day
golang.org/x/tools v0.1.1 CANDIDATE Correlated change; unproven combination builds observed 1 project-day
golang.org/x/xerrors v0.0.0-20200804184101-5ec99f83aff1 CANDIDATE Correlated change; unproven combination contract passed 1 project-day

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.4.2v0.3.0v0.2.0v0.1.1-0.20191105210325-c90efee705eev0.0.0-20190513183733-4bf6d317e70e
golang.org/x/crypto — — — — — — — — v0.3.0 v0.0.0-20191011191535-87dc89f01550 v0.0.0-20191011191535-87dc89f01550 v0.0.0-20191011191535-87dc89f01550 v0.0.0-20210711020723-a769d52b0f97 v0.0.0-20190510104115-cbcb75029529
golang.org/x/tools v0.49.0 v0.48.0 v0.46.0 v0.44.0 v0.31.0 v0.22.0 v0.14.0 v0.1.12 v0.1.12 v0.1.1 v0.0.0-20200825202427-b303f430e36d v0.0.0-20200331025713-a30bf2db82d4 — —
golang.org/x/xerrors — — — — — — — — — v0.0.0-20200804184101-5ec99f83aff1 v0.0.0-20200804184101-5ec99f83aff1 v0.0.0-20191204190536-9bdfabe68543 v0.0.0-20200804184101-5ec99f83aff1 —

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