CodeSampleX

Recordsgolanggithub.com/kr/textv0.1.0

Change the conditions
Fixed
OSlinux Package versionv0.1.0 Package managergo
Filter Runtimego 1.26 Symbolwhole package Architecturex64 Execution contextgo libcglibc Clear filters

Current conditions

github.com/kr/text @v0.1.0linux · 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.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
13
Independent reporting peers
1
Last recorded
2026-09-17

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

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.

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