Records/golang/gopkg.in/yaml.v3/v3.0.1/sigs.k8s.io/yaml.UnmarshalStrict

shared with 2 packages — this evidence cannot say whose API it is

Published samples

• gopkg.in/yaml.v3 v3.0.1: Decode YAML with sigs.k8s.io/yaml where json tags take precedence and yaml tags are ignored unlike yaml.v3 Built ? 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. HOWsigs.k8s.io/yaml.Unmarshalsigs.k8s.io/yaml.UnmarshalStrictgopkg.in/yaml.v3.Unmarshalgo MIT-0 · 2026-08-15

Compatibility matrix

Project-level observations and symbol/contract verifications are counted separately and never combined.

These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.

snapshot · 2026-09-15

Failure clusters

• observed PROJECT_TEST Evidence gap ×3 v3.0.1 os=windows · runtime=go@1.26
  Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-19 · Last seen: 2026-08-19
  Diagnostic re-verification candidate
  Where does this failure start and stop?
• 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 run
  Evidence quality: complete · Environment variants: 1 · First recorded: 2026-09-03 · Last seen: 2026-09-03
  Where does this failure start and stop?