Sample
yaml 2.9.0: identify YAML AST node types using type guard functions
Verified sample for npm yaml 2.9.0: identify YAML AST node types using type guard functions. The contract ran on node 22 · linux alpine/x64 · docker and…
sha256:43be9c1b6fa308424bbb38218e40a648359526865949dc4c856af8e50a42e924
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
- 1
- Signing keys that built it
- 1
Declared environment
windows 11 x64 npm
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-19 |
Case
HOW- Goal
- identify YAML AST node types using type guard functions
- Packages
- Symbols
-
- isMap
- isNode
- isScalar
- isSeq
- Created
- 2026-08-19T02:52:09Z
Contract
- isNode returns true for YAML AST Node instances including Scalar, YAMLMap, and YAMLSeq
- isScalar returns true for scalar AST nodes representing primitive values
- isMap returns true for mapping AST nodes representing key-value collections
- isSeq returns true for sequence AST nodes representing ordered lists
- Type guards return false for non-AST objects, primitives, and null
Files
- PROMPT.md
- csx.json
- index.mjs
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous