Recordsgolanggithub.com/mattn/go-isattyv0.0.12
Change the conditions
Current conditions
github.com/mattn/go-isatty @v0.0.12ubuntu glibc · x64 · go 1.26 · go 1
package-level total, not an API
2 of 2 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
- 2 / 2
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-15
Dependency Health
Observed combinations and failure evidence for this release
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.
| Library | v0.0.24 | v0.0.20 | v0.0.17 | v0.0.12 | v0.0.11 | v0.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.