CodeSampleX

Recordsgolanggithub.com/mattn/go-isattyv0.0.20

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

Current conditions

github.com/mattn/go-isatty @v0.0.20debian 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.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-16
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Steady 0

First observed break

v0.0.20

go@1.26

278 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
golang.org/x/sys v0.31.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
golang.org/x/sys v0.41.0 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
golang.org/x/sys v0.45.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
golang.org/x/sys v0.46.0 CANDIDATE Correlated change; unproven combination builds observed 3 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.0.24v0.0.20v0.0.17v0.0.12v0.0.11v0.0.7
golang.org/x/sys v0.47.0 v0.31.0 v0.7.0 v0.18.0 v0.0.0-20191026070338-33540a1f6037 v0.0.0-20210615035016-665e8c7367d1

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