CodeSampleX

Recordsgolanggithub.com/kr/textv0.1.0

Change the conditions
Fixed
Package versionv0.1.0 Package managergo 1
Filter OSubuntu glibc Runtimego 1.26 Symbolwhole package Architecturex64 libcglibc Clear filters

Current conditions

github.com/kr/text @v0.1.0ubuntu glibc · x64 · go 1.26 · go 1

package-level total, not an API

0 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 failed

Project observations
4 / 4
Contract verifications
0 / 1
Usage records
6
Independent reporting peers
1
Last recorded
2026-09-03
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Unknown 2 · Steady 1

First observed break

v0.1.0

linux · go@1.26

2 FAIL · stage: UNKNOWN · fingerprint: sha256:00e630595b1ef857fd5ae5d542be8e69553193e64d7aa9c19d7a0623012e7f90

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/kr/pty v1.1.1 UNKNOWN No linked outcome measured nothing measured 59 project-days
github.com/kr/pty v1.1.3 UNKNOWN No linked outcome measured nothing measured 6 project-days
github.com/kr/pty v1.1.8 PASS All observations passed contract passed 20 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.2.0v0.1.0
github.com/creack/pty v1.1.9 —
github.com/kr/pty — v1.1.3

Moved: 0 · unchanged at every release: 2

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