CodeSampleX

Recordsgolanggolang.org/x/textv0.14.0

Change the conditions
Fixed
OSdebian glibc Package versionv0.14.0 Symbolwhole package
Filter Runtimego 1.26 Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

golang.org/x/text @v0.14.0debian 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.

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

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
2
Independent reporting peers
1
Last recorded
2026-09-03
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 0

First observed break

v0.14.0 golang.org/x/tools@v0.6.0

linux · go@1.26

6 FAIL · stage: PROJECT_PROCESS

View exact conditions View failure cluster
Library Version Health Measured there Projects
golang.org/x/tools v0.6.0 FAIL Linked failure observed; version changed across releases builds observed 6 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.41.0v0.40.0v0.37.0v0.36.0v0.35.0v0.34.0v0.22.0v0.21.0v0.14.0v0.5.0v0.3.6v0.3.2
golang.org/x/tools v0.48.0 v0.47.0 v0.44.0 v0.44.0 v0.42.0 v0.41.0 v0.21.1-0.20240508182429-e35e4ccd0d2d v0.21.1-0.20240508182429-e35e4ccd0d2d v0.6.0 v0.1.12 v0.0.0-20200825202427-b303f430e36d v0.0.0-20180917221912-90fa682c2a6e
golang.org/x/mod — — — — — — — — — v0.6.0-dev.0.20220419223038-86c51ed26bb4 — —
golang.org/x/sys — — — — — — — — — v0.47.0 — —

Moved: 1 · unchanged at every release: 2

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