CodeSampleX

Recordsgolanggolang.org/x/text

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

Current conditions

golang.org/x/text @v0.23.0debian glibc · x64 · go 1.26 · go · go

2 of 2 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (4)

Project observations
6 / 6
Contract verifications
2 / 2
Usage records
4
Independent reporting peers
1
Last recorded
2026-09-17

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

v0.23.0

24 FAIL · stage: PROCESS_START · fingerprint: sha256:c12549970456efb5abdc90b679695c6689107d4f097d612245d6bfb25e01ec32

Library Version Health Measured there Projects
golang.org/x/tools v0.21.1-0.20240508182429-e35e4ccd0d2d CANDIDATE Correlated change; unproven combination nothing measured 2 project-days
golang.org/x/tools v0.31.0 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.42.0v0.41.0v0.40.0v0.38.0v0.37.0v0.36.0v0.35.0v0.34.0v0.33.0v0.32.0v0.31.0v0.29.0v0.28.0v0.27.0v0.26.0v0.25.0v0.24.0v0.23.0v0.22.0v0.21.0v0.20.0v0.17.0v0.16.0v0.14.0v0.13.0v0.12.0v0.11.0v0.5.0v0.4.0v0.3.7v0.3.6v0.3.3v0.3.2
golang.org/x/sys — — — — — — — — — — — — — — — — — — — — — — — — — — — v0.47.0 v0.2.0 — — — —
golang.org/x/tools v0.49.0 v0.48.0 v0.47.0 v0.45.0 v0.44.0 v0.44.0 v0.42.0 v0.41.0 v0.41.0 v0.39.0 v0.38.0 v0.36.0 v0.35.0 v0.34.0 v0.33.0 v0.21.1-0.20240508182429-e35e4ccd0d2d v0.21.1-0.20240508182429-e35e4ccd0d2d v0.31.0 v0.21.1-0.20240508182429-e35e4ccd0d2d v0.21.1-0.20240508182429-e35e4ccd0d2d v0.47.0 v0.21.1-0.20240508182429-e35e4ccd0d2d v0.2.0 v0.6.0 v0.14.0 v0.6.0 v0.6.0 v0.1.12 v0.1.12 v0.1.12 v0.0.0-20200825202427-b303f430e36d v0.0.0-20200825202427-b303f430e36d v0.0.0-20200618134242-20370b0cb4b2
golang.org/x/mod — — — — — — — — — — — — — — — — — — — — — — — — — — — v0.6.0-dev.0.20220419223038-86c51ed26bb4 v0.6.0-dev.0.20220419223038-86c51ed26bb4 — — — —

Moved: 2 · unchanged at every release: 1

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.