CodeSampleX

Recordsgolanggithub.com/kr/prettyv0.2.1

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

Current conditions

github.com/kr/pretty @v0.2.1debian 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
2
Independent reporting peers
1
Last recorded
2026-09-04
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

v0.2.1

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/text v0.1.0 CANDIDATE Correlated change; unproven combination contract passed 8 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.3.1v0.2.1v0.2.0v0.1.0
github.com/kr/text v0.2.0 v0.1.0 v0.1.0 v0.1.0
github.com/rogpeppe/go-internal v1.9.0 — — —

Moved: 1 · unchanged at every release: 1

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