CodeSampleX

Recordsgolanggithub.com/go-kit/logv0.1.0github.com/go-kit/log.Logger

Change the conditions
Fixed
Symbolgithub.com/go-kit/log.Logger Architecturex64 Package managergo
Filter OSdebian glibc Runtimego 1.26 Package versionv0.1.0 Execution contextgo libcglibc Clear filters

Current conditions

github.com/go-kit/log.Logger @v0.1.0debian glibc · 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 (1)

Project observations
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 1

First observed break

v0.1.0

linux · go@1.26

1 FAIL · stage: UNKNOWN · fingerprint: sha256:042f6e977a16262a7e633b3137ce9291be598b66496d9201e447ee2b8efa6eb8

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/go-logfmt/logfmt v0.5.0 CANDIDATE Correlated change; unproven combination contract passed 53 project-days
github.com/go-stack/stack v1.8.0 PASS All observations passed contract passed 53 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