CodeSampleX

Recordsgolanggopkg.in/yaml.v3v3.0.1yaml.DuplicateKeyError

Change the conditions
Fixed
OSlinux Symbolyaml.DuplicateKeyError
Filter Runtimego 1.26 Package versionv3.0.1 Architecturex64 Package managergomod Execution contextgo libcmusl Clear filters

Current conditions

yaml.DuplicateKeyError @v3.0.1linux · musl · x64 · go 1.26 · gomod · 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
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-09-08
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Steady 1

First observed break

v3.0.1

windows · go@1.26

3 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
gopkg.in/check.v1 v0.0.0-20161208181325-20d25e280405 CANDIDATE Correlated change; unproven combination contract passed 36 project-days
gopkg.in/check.v1 v1.0.0-20180628173108-788fd7840127 CANDIDATE Correlated change; unproven combination nothing measured 8 project-days
gopkg.in/check.v1 v1.0.0-20190902080502-41f04d3bba15 CANDIDATE Correlated change; unproven combination nothing measured 8 project-days
gopkg.in/check.v1 v1.0.0-20201130134442-10cb98267c6c CANDIDATE Correlated change; unproven combination contract passed 134 project-days
sigs.k8s.io/yaml v1.4.0 PASS All observations passed contract passed 1 project-day

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.

Libraryv3.0.1v3.0.0-20200313102051-9f266ea9e77c
gopkg.in/check.v1 v1.0.0-20190902080502-41f04d3bba15 v1.0.0-20180628173108-788fd7840127
sigs.k8s.io/yaml v1.4.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