Recordsgolangsigs.k8s.io/yamlv1.6.0yaml.Marshal
Change the conditions
Current conditions
yaml.Marshal @v1.6.0alpine musl · x64 · go 1.26 · go · go
3 of 3 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
- 3 / 3
- 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
All 3 dependencies report steady passing evidence.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| sigs.k8s.io/randfill | v1.0.0 | UNKNOWN No linked outcome measured | nothing measured | 2 project-days |
| github.com/google/go-cmp | v0.5.9 | PASS All observations passed | contract passed | 2 project-days |
| go.yaml.in/yaml/v2 | v2.4.2 | PASS All observations passed | contract passed | 2 project-days |
| go.yaml.in/yaml/v3 | v3.0.3 | PASS All observations passed | builds observed | 2 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.
| Library | v1.6.0 | v1.5.0 | v1.4.0 |
|---|---|---|---|
| github.com/google/go-cmp | v0.5.9 | v0.5.9 | v0.5.9 |
| go.yaml.in/yaml/v2 | v2.4.2 | v2.4.2 | — |
| go.yaml.in/yaml/v3 | v3.0.3 | v3.0.3 | — |
| gopkg.in/check.v1 | — | — | v0.0.0-20161208181325-20d25e280405 |
| sigs.k8s.io/randfill | v1.0.0 | — | — |
Moved: 0 · 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.