Sample
yaml 2.9.0: Resolve YAML merge keys (<<) into target objects without mangling YAML 1.2 boolean-like string keys via merge: true
Verified sample for npm yaml 2.9.0: Resolve YAML merge keys (<<) into target objects without mangling YAML 1.2 boolean-like string keys via merge: true. The…
sha256:8db34c60cda5539552b616020f390fb44a01a7812ac77f3025a001e31666e5da
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 many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 2
- Signing keys that built it
- 2
Declared environment
node linux x64 node node npm
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-16 |
| node 22 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-18 |
Case
HOW- Goal
- Resolve YAML merge keys (<<) into target objects without mangling YAML 1.2 boolean-like string keys via merge: true
- Packages
- Symbols
-
- yaml.parse
- yaml.parseDocument
- Environment
- node
- Created
- 2026-08-16T07:08:23Z
Contract
- YAML.parse(doc) in default YAML 1.2 core schema leaves '<<' as an unmerged literal property and leaves inherited properties undefined
- YAML.parse(doc, { schema: 'yaml-1.1' }) resolves merge keys but coerces string keys like 'y' and 'no' into boolean keys true and false
- YAML.parse(doc, { merge: true }) resolves single and multi-merge anchor keys into the target mapping while preserving YAML 1.2 string keys and removing '<<'
- Explicit target properties override merged properties, and earlier merge mappings override later ones in array merge syntax
- YAML.parseDocument(doc, { merge: true }).toJS() merges keys identically with zero document errors
Files
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs