CodeSampleX

Recordsgolanggolang.org/x/termv0.40.0golang.org/x/term.GetSize

Change the conditions
Fixed
OSdebian glibc Symbolgolang.org/x/term.GetSize Architecturex64
Filter Runtimego 1.26 Package versionv0.40.0 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

golang.org/x/term.GetSize @v0.40.0debian glibc · x64 · go 1.26 · go · go

1 of 1 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 (1)

Project observations
2 / 2
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Changed 1 · Steady 0

Dependency changes observed: 1. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
golang.org/x/sys v0.41.0 CHANGED Version changed, no linked failure 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.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.43.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.