CodeSampleX

Recordsgolanggo.uber.org/zapv1.13.0go.uber.org/zap.Hooks

Change the conditions
Fixed
OSubuntu glibc Package versionv1.13.0 Symbolgo.uber.org/zap.Hooks
Filter Runtimego 1.26 Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

go.uber.org/zap.Hooks @v1.13.0ubuntu glibc · x64 · go 1.26 · go 1

1 of 1 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
1 / 1
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-15

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 5

First observed break

v1.13.0

linux · go@1.26

1 FAIL · stage: UNKNOWN · fingerprint: sha256:cc6da42c69d5a8040f6a9dbda27d7d8e0daef42f5c34d1da8e73713061384c8d

Library Version Health Measured there Projects
github.com/stretchr/testify v1.4.0 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
github.com/stretchr/testify v1.7.0 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
github.com/stretchr/testify v1.8.1 CANDIDATE Correlated change; unproven combination contract passed 11 project-days
go.uber.org/multierr v1.3.0 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
go.uber.org/multierr v1.5.0 CANDIDATE Correlated change; unproven combination contract passed 16 project-days
github.com/pkg/errors v0.8.1 PASS All observations passed contract passed 21 project-days
github.com/pkg/errors v0.9.1 PASS All observations passed contract passed 1 project-day
go.uber.org/atomic v1.5.0 PASS All observations passed contract passed 4 project-days
go.uber.org/atomic v1.6.0 PASS All observations passed contract passed 16 project-days
golang.org/x/lint v0.0.0-20190930215403-16217165b5de 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: 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