CodeSampleX

Recordsgolanggolang.org/x/expv0.0.0-20230515195305-f3d0a9c9a5cc

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

Current conditions

golang.org/x/exp @v0.0.0-20230515195305-f3d0a9c9a5ccubuntu glibc · x64 · go 1.26 · go 1

package-level total, not an API

9 of 17 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
9 / 17
Contract verifications
nothing at this coordinate
Usage records
3
Independent reporting peers
2
Failures with a captured fingerprint
1 / 8
Last recorded
2026-08-30
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Steady 0

First observed break

v0.0.0-20230515195305-f3d0a9c9a5cc

linux · go@1.26

8 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/google/go-cmp v0.5.8 CANDIDATE Correlated change; unproven combination nothing measured 3 project-days
github.com/google/go-cmp v0.6.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
golang.org/x/mod v0.6.0 CANDIDATE Correlated change; unproven combination nothing measured 4 project-days
golang.org/x/tools v0.2.0 CANDIDATE Correlated change; unproven combination nothing measured 4 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.0.0-20260824195058-e88cd73687aav0.0.0-20251023183803-a4bb9ffd2546v0.0.0-20240506185415-9bf2ced13842v0.0.0-20230515195305-f3d0a9c9a5ccv0.0.0-20200224162631-6cc2880d07d6
github.com/google/go-cmp v0.6.0 v0.7.0 v0.6.0 v0.6.0 —
golang.org/x/mod v0.39.0 v0.37.0 v0.17.0 v0.6.0 v0.2.0
golang.org/x/tools v0.49.0 v0.46.0 v0.21.0 v0.2.0 v0.0.0-20200825202427-b303f430e36d
dmitri.shuralyov.com/gpu/mtl — — — — v0.0.0-20190408044501-666a987793e9
github.com/BurntSushi/xgb — — — — v0.0.0-20160522181843-27f122750802
github.com/go-gl/glfw/v3.3/glfw — — — — v0.0.0-20200222043503-6f7a984d4dc4
golang.org/x/image — — — — v0.0.0-20190802002840-cff245a6509b
golang.org/x/mobile — — — — v0.0.0-20190719004257-d2bd2a29d028
golang.org/x/sys — — — — v0.47.0
golang.org/x/tools/go/packages/packagestest v0.1.1-deprecated v0.1.1-deprecated — — —
golang.org/x/xerrors — — — — v0.0.0-20200804184101-5ec99f83aff1

Moved: 3 · unchanged at every release: 8

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