CodeSampleX

Recordsgolanggithub.com/mattn/go-isattyv0.0.12github.com/mattn/go-isatty.IsCygwinTerminal

Change the conditions
Fixed
Package versionv0.0.12 Symbolgithub.com/mattn/go-isatty.IsCygwinTerminal
Filter OSdebian glibc Runtimego 1.26 Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

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

Dependency Health

Observed combinations and failure evidence for this release

Changed 4 · Steady 0

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

Library Version Health Measured there Projects
golang.org/x/sys v0.0.0-20200116001909-b77594299b42 CHANGED Version changed, no linked failure builds observed 1 project-day
golang.org/x/sys v0.0.0-20210615035016-665e8c7367d1 CHANGED Version changed, no linked failure contract passed 7 project-days
golang.org/x/sys v0.17.0 CHANGED Version changed, no linked failure contract passed 9 project-days
golang.org/x/sys v0.18.0 CHANGED Version changed, no linked failure 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: 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.