Recordsgolanggopkg.in/yaml.v3v3.0.1sigs.k8s.io/yaml.UnmarshalStrict
Change the conditions
Current conditions
sigs.k8s.io/yaml.UnmarshalStrict @v3.0.1linux · musl · x64 · go 1.26 · gomod · go
2 of 2 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
- 2 / 2
- Independent reporting peers
- 1
- Cross-checked
- reproduced by two or more independent peers
- Last recorded
- 2026-09-08
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v3.0.1
windows · go@1.26
3 FAIL · stage: PROJECT_TEST
| 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.
| Library | v3.0.1 | v3.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
-
observed PROJECT_RESOLVE exit 1 ×1 v3.0.1 os=linux · runtime=go@1.26 sha256:0d0008e28623…<path>:<n>:<n>: missing go.sum entry for module providing package github.com/stretchr/objx (imported by github.com/stretchr/testify/mock); to add:go/module · resolve-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-03 · Last seen: 2026-09-03