Recordsnpmjs-yaml3.15.1
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
| alpine musl | ubuntu glibc | 11 | |
|---|---|---|---|
| js-yaml.FAILSAFE_SCHEMA | 100%1 | ||
| js-yaml.YAMLException | 100%1 | ||
| js-yaml.safeDump | 100%2 | ||
| js-yaml.safeLoad | 100%2 | ||
| js-yaml.safeLoadAll | 100%2 |
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.
Environment detail
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
Observations: PROJECT_LOAD 1✓ · PROJECT_TEST 1✓ — Usage: USED 1✓ — Verified: CONTRACT 1✓
|
LOW | 2 +1 | 1 | 100% | 1 · 1✓ | 2026-08-30 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 5✓
|
MEDIUM | 5 | 0 | 100% | 2 | 2026-08-29 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 4✓
|
LOW | 4 | 0 | 100% | 1 | 2026-08-16 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 5✓ 5✕
|
ELEVATED FAILURE | 10 | 0 | 50% | 1 | 2026-08-16 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 1✓
|
LOW | 1 | 0 | 100% | 1 | 2026-08-16 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 8✓ · PROJECT_TEST 2✓ 3✕ — Usage: USED 1✓
|
LOW | 13 +1 | 0 | 77% | 1 | 2026-08-18 |
Recent failure clusters
-
observed PROJECT_PROCESS ERR_MODULE_NOT_FOUND Evidence gap ×14 3.15.1 → 4.1.0 → 4.3.1 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 6 · First recorded: 2026-08-16 · Last seen: 2026-08-29Diagnostic re-verification candidate
-
observed PROJECT_TEST ENOENT Evidence gap ×7 3.15.1 → 4.3.0 → 4.3.1 executionContext=node · os=windows · runtime=node@24.13Evidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-17 · Last seen: 2026-08-25Diagnostic re-verification candidate
Symbols
Published samples
- js-yaml 3.15.1 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. HOWnode 22.23.2 MIT-0 · 2026-08-24