Recordsgolanggopkg.in/yaml.v3failure issue
Failure signature
PROJECT_RESOLVE exit 1 ×1
<path>:<n>:<n>: missing go.sum entry for module providing package github.com/stretchr/objx (imported by github.com/stretchr/testify/mock); to add:
Evidence quality: complete · go/module · resolve-diagnostic · outer go run · First recorded: 2026-09-03 · Last seen: 2026-09-03
sha256:0d0008e28623…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_RESOLVE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v3.0.1 FAIL
- v3.0.0-20200313102051-9f266ea9e77c not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-03 → 2026-09-03
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
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.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_RESOLVE.
- Releases in this window never measured at PROJECT_RESOLVE: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- gopkg.in/yaml.v3 v3.0.1 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-08-23
- gopkg.in/yaml.v3 v3.0.1: Unmarshal YAML documents into yaml.Node AST where top-level mappings are wrapped in a DocumentNode and mapping entries are stored as a flat slice of alternating key and value nodes. This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWyaml.Nodeyaml.Unmarshalyaml.Node.Decodego MIT-0 · 2026-08-17
- gopkg.in/yaml.v3 v3.0.1: Enabling Decoder.KnownFields(true) returns a yaml.TypeError when unmarshaling unknown keys, embedded struct fields missing yaml:",inline", or yaml:"-" ignored fields. This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWyaml.Decoder.KnownFieldsgo MIT-0 · 2026-08-17