CodeSampleX

Recordsgolanggolang.org/x/termv0.43.0

Change the conditions
Fixed
OSwindows 11 Package versionv0.43.0
Filter Runtimego 1.26 Symbolwhole package Architecturex64 Package managergo 1 Clear filters

Current conditions

golang.org/x/term @v0.43.0windows 11 · x64 · go 1.26 · go 1

package-level total, not an API

7 of 9 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
7 / 9
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Failures with a captured fingerprint
0 / 2
Last recorded
2026-08-18
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

v0.43.0

go@1.26

3 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
golang.org/x/sys v0.45.0 CANDIDATE Correlated change; unproven combination contract passed 2 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.45.0v0.43.0v0.42.0v0.41.0v0.40.0v0.22.0v0.17.0v0.2.0v0.0.0-20210927222741-03fcf44c2211v0.0.0-20201126162022-7de9c90e9dd1
golang.org/x/sys v0.47.0 v0.45.0 v0.44.0 v0.42.0 v0.41.0 v0.22.0 v0.17.0 v0.2.0 v0.0.0-20210615035016-665e8c7367d1 v0.47.0

Moved: 1 · unchanged at every release: 0

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