Recordsgolangsigs.k8s.io/yamlv1.6.0yaml.Marshal
shared with 4 packages — this evidence cannot say whose API it is
Published samples
- sigs.k8s.io/yaml v1.6.0: sigs.k8s.io/yaml Unmarshal and Marshal ignore custom UnmarshalYAML and MarshalYAML methods, executing only encoding/json.Unmarshaler and encoding/json.Marshaler implementations due to intermediate JSON conversion. 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.Unmarshalyaml.Marshalgo MIT-0 · 2026-08-17
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.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| go 1.26 · Go · go · linux musl · docker
Observations: PROJECT_TEST 1✓ — Verified: CONTRACT 3✓
|
HIGH | 1 | 3 | 100% | 1 · 3✓ | 2026-09-08 |
snapshot · 2026-09-15
Failure clusters
No failure clusters observed.