CodeSampleX

Recordsgolanggolang.org/x/termv0.34.0

Change the conditions
Fixed
OSlinux Package versionv0.34.0
Filter Runtimenode 22 Symbolwhole package Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

golang.org/x/term @v0.34.0linux · glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 3 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
9 / 9
Contract verifications
0 / 3
Usage records
8
Independent reporting peers
2
Last recorded
2026-08-30
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.0.0-20210927222741-03fcf44c2211

linux · node@22.23 · executionContext=node · moduleSystem=cjs

6 FAIL · stage: PROJECT_PROCESS

View exact conditions View failure cluster

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.

Recent failure clusters