CodeSampleX

Recordsgolanggo.uber.org/zapv1.27.0

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

Current conditions

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

there is a sample here, and nothing of ours has run it at this coordinate yet (3)

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-07

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 1

First observed break

v1.27.0

go@1.26

5 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
github.com/stretchr/testify v1.8.1 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
go.uber.org/goleak v1.3.0 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
go.uber.org/multierr v1.10.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
gopkg.in/yaml.v3 v3.0.1 PASS All observations passed contract passed 5 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

Showing the 12 most-reported of 15 recorded failure clusters. The rest are single reports.