CodeSampleX

Recordsgolanggolang.org/x/textv0.36.0

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

Current conditions

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

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-01

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 2 · Steady 0

First observed break

v0.36.0 golang.org/x/tools@v0.43.0

linux · go@1.26

1 FAIL · stage: PROJECT_TEST · fingerprint: sha256:60421cf615fff552906c1e3ad66d19b70255ceb1ed79b3d21292facfed91efa8

Library Version Health Measured there Projects
golang.org/x/tools v0.43.0 FAIL Linked failure observed; version changed across releases builds observed 1 project-day
golang.org/x/tools v0.44.0 FAIL Linked failure observed; version changed across releases 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.

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