CodeSampleX

Recordsgolanggolang.org/x/textv0.3.5

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

Current conditions

golang.org/x/text @v0.3.5ubuntu glibc · x64 · go 1.26 · go 1

package-level total, not an API

0 of 8 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed

Project observations
8 / 9
Contract verifications
0 / 8
Usage records
18
Independent reporting peers
1
Last recorded
2026-10-25
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

v0.3.5

linux · go@1.26

8 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:d5fae02e8604b6955b8f1c65a8d5cc795aaceed9651a9f67da2c34536a6764a1

View exact conditions View failure cluster
Library Version Health Measured there Projects
golang.org/x/tools v0.0.0-20210108195828-e2f9c7f1fc8e CANDIDATE Correlated change; unproven combination contract passed 6 project-days
golang.org/x/tools v0.1.5 CANDIDATE Correlated change; unproven combination contract passed 9 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.43.0v0.42.0v0.41.0v0.40.0v0.38.0v0.37.0v0.36.0v0.35.0v0.34.0v0.33.0v0.32.0v0.31.0v0.30.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.8v0.3.7v0.3.6v0.3.5v0.3.4v0.3.3v0.3.2
golang.org/x/sys — — — — — — — — — — — — — — — — — — — — — — — — — — — — — v0.47.0 v0.0.0-20220722155257-8c9f86f7a55f — — — — — — —
golang.org/x/tools v0.51.0 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.37.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.1.12 v0.0.0-20200825202427-b303f430e36d v0.0.0-20210108195828-e2f9c7f1fc8e v0.0.0-20201208233053-a543418bbed2 v0.0.0-20210105154028-b0ab187a4818 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.

Recent failure clusters