Recordsnpmyaml2.9.0Document
OS × runtime at a glance
1○ 12026-08-27
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Published samples
- yaml 2.9.0: Merge YAML mapping keys with merge option and schema yaml-1.1 using parse and parseDocument 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. HOWDocumentparseparseDocument MIT-0 · 2026-08-27
- yaml 2.9.0: Manage YAML nested collections and nodes with getIn, setIn, and deleteIn 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. HOWDocumentdeleteIngetInsetInnode MIT-0 · 2026-08-19
- yaml 2.9.0: create and modify YAML Document with Document 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. HOWDocumentnode 22.23.2 MIT-0 · 2026-08-18
- yaml 2.9.0: Modify YAML AST and preserve comments using Document and parseDocument 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. HOWDocumentparseDocumentnode MIT-0 · 2026-08-18
- yaml 2.9.0: Parse YAML configurations with yaml v2 avoiding silent truthiness traps from unquoted yes/no/on/off strings, unmerged << merge keys, and decimal-parsed leading-zero permissions 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.Documentyaml.parseyaml.parseDocumentyaml.stringifynode MIT-0 · 2026-08-16
- yaml 2.9.0: Manipulate YAML Document AST paths, preserve comments, control scalar styles, and transform nodes with visit in yaml 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.parseDocumentyaml.Documentyaml.visityaml.Scalarnode 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 |
|---|---|---|---|---|---|---|
| node 22 · JS · npm · linux musl · docker
Verified: CONTRACT 1✓
|
LOW | 0 | 1 | 100% | 0 · 1✓ | 2026-08-27 |
| node 22 · JS · npm · linux musl · docker
Verified: CONTRACT 3✓
|
LOW | 0 | 3 | 100% | 0 · 1✓ | 2026-08-19 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 2✓
|
LOW | 2 | 0 | 100% | 1 | 2026-08-17 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 7✓ 4✕
|
ELEVATED FAILURE | 11 | 0 | 64% | 1 | 2026-08-17 |
snapshot · 2026-08-30
Failure clusters
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×5 2.9.0 executionContext=node · os=windows · runtime=node@24.13Evidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-17 · Last seen: 2026-08-17Diagnostic re-verification candidate