CodeSampleX

Recordsgolanggithub.com/go-kit/logv0.2.1github.com/go-kit/log.NewLogfmtLogger

Change the conditions
Fixed
OSalpine musl Package versionv0.2.1 Symbolgithub.com/go-kit/log.NewLogfmtLogger
Filter Runtimego 1.26 Architecturex64 Package managergo Execution contextgo libcmusl Clear filters

Current conditions

github.com/go-kit/log.NewLogfmtLogger @v0.2.1alpine musl · 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 (2)

Project observations
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-26
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

1 FAIL · stage: PROJECT_PROCESS

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/go-logfmt/logfmt v0.5.1 CANDIDATE Correlated change; unproven combination contract passed 4 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.1v0.2.0v0.1.0
github.com/go-logfmt/logfmt v0.5.1 v0.5.1 v0.5.0
github.com/go-stack/stack — — v1.8.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