CodeSampleX

Recordsgolanggopkg.in/yaml.v2v2.3.0yaml.NewEncoder

Change the conditions
Fixed
Symbolyaml.NewEncoder Package managergo
Filter OSdebian glibc Runtimego 1.26 Package versionv2.3.0 Architecturex64 Execution contextgo libcglibc Clear filters

Current conditions

yaml.NewEncoder @v2.3.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 2 · Steady 0

First observed break

v2.3.0

linux

3 FAIL · stage: UNKNOWN · fingerprint: sha256:9922ca80f240bbcc7904b679943bbc3e6a9f08fa3dc0e823aadcc4450e6a4830

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 13 project-days
gopkg.in/check.v1 v1.0.0-20190902080502-41f04d3bba15 CANDIDATE Correlated change; unproven combination nothing measured 15 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.

Libraryv2.4.0v2.3.0v2.2.2v2.2.1
gopkg.in/check.v1 v1.0.0-20190902080502-41f04d3bba15 v0.0.0-20161208181325-20d25e280405 v1.0.0-20190902080502-41f04d3bba15 v0.0.0-20161208181325-20d25e280405

Moved: 1 · unchanged at every release: 0

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