Sample
yaml 2.9.0: Handle YAML 1.2 boolean string coercion, merge key resolution, multi-document parsing errors, duplicate key constraints, and line width folding in yaml
Verified sample for npm yaml 2.9.0: Handle YAML 1.2 boolean string coercion, merge key resolution, multi-document parsing errors, duplicate key constraints…
sha256:2599e0d3b97c21e59a6f4de52c39dc7235d8c59d64db5fa9519e8114c1e197e6
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
- Handle YAML 1.2 boolean string coercion, merge key resolution, multi-document parsing errors, duplicate key constraints, and line width folding in yaml
- Packages
- Symbols
-
- yaml.parse
- yaml.stringify
- yaml.parseAllDocuments
- Environment
- node
- Created
- 2026-08-16T07:08:23Z
Contract
- yaml.parse parses yes/no/on/off as strings under default YAML 1.2 Core schema unless schema: yaml-1.1 is configured
- yaml.parse keeps merge key << as literal property unless merge: true is explicitly enabled
- yaml.parse throws MULTIPLE_DOCS error on multi-document YAML requiring yaml.parseAllDocuments
- yaml.parse throws DUPLICATE_KEY error on duplicate mapping keys unless uniqueKeys: false is set
- yaml.stringify wraps long lines at column 80 unless lineWidth: 0 is configured
- yaml.stringify indents sequence items under mapping keys by default unless indentSeq: false is configured
Files
- NOTES.md
- csx.json
- package-lock.json
- package.json
- src/index.mjs
- test/contract.mjs