CodeSampleX

Recordsgolanggo.uber.org/zapv1.28.0go.uber.org/zap.Field

Change the conditions
Fixed
Symbolgo.uber.org/zap.Field Package managergo
Filter OSdebian glibc Runtimego 1.26 Package versionv1.28.0 Architecturex64 Execution contextgo libcglibc Clear filters

Current conditions

go.uber.org/zap.Field @v1.28.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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 1

First observed break

v1.28.0

go@1.26

5 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
github.com/stretchr/testify v1.11.1 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
github.com/stretchr/testify v1.8.1 CANDIDATE Correlated change; unproven combination contract passed 11 project-days
go.uber.org/goleak v1.3.0 CANDIDATE Correlated change; unproven combination contract passed 11 project-days
go.uber.org/multierr v1.10.0 CANDIDATE Correlated change; unproven combination contract passed 11 project-days
go.uber.org/multierr v1.11.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
go.yaml.in/yaml/v3 v3.0.4 PASS All observations passed contract passed 13 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: 3 · unchanged at every release: 5

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