Recordsnpmjs-yaml4.3.1js-yaml.load
OS × runtime at a glance
22026-08-29
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.
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.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 4✓ — Verified: UNKNOWN 0✓ 3✕
|
ELEVATED FAILURE | 4 | 3 | 57% | 1 | 2026-08-29 |
| node 24.13 · JS · pnpm · windows
Observations: PROJECT_COMPILE 8✓ · PROJECT_TEST 14✓ 2✕ — Verified: UNKNOWN 0✓ 2✕
|
LOW | 24 | 2 | 85% | 1 | 2026-08-29 |
snapshot · 2026-08-30
Failure clusters
-
observed PROJECT_PROCESS ERR_ASSERTION 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
-
observed PROJECT_TYPECHECK Evidence gap ×2 4.3.0 → 4.3.1 executionContext=node · moduleSystem=cjs · os=windowsEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-20 · Last seen: 2026-08-21Diagnostic re-verification candidate
-
observed PROJECT_TEST exit 1 ERR_ASSERTION ×2 4.3.1 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:45fc70285a65…Contract test failed: AssertionError [ERR_ASSERTION]: DOWNLOAD_PROGRESS event should have fired · false !== true · at main (<path>:<n>:<n>) { …javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29
-
observed PROJECT_TEST Evidence gap ×1 4.3.1 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 js-yaml.loadEvidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-25 · Last seen: 2026-08-25
-
observed UNKNOWN exit 1 Evidence gap ×1 4.3.1 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 js-yaml.load sha256:8310a83be884…node:internal/modules/cjs/loader:<n> · const err = new Error(message); · ^ · Error: Cannot find module <str>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_MODULE_NOT_FOUND Evidence gap ×1 4.3.1 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 js-yaml.load sha256:88af852f99a8…node:internal/modules/package_json_reader:<n> · throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null); · ^ …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 4.3.1 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:8e2ccedae0ba…Contract test failed: TypeError: this.doDownloadUpdate is not a function · at CustomBaseUpdater.downloadUpdate <path>:<n>:<n>) · at main (<path>:<n>:<n>) …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 4.3.1 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:91ad26545eb1…node:internal/modules/cjs/loader:<n> · throw err; · ^ · Error: Cannot find module <str>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 4.3.1 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:91bb8f54cd90…Contract test failed: Error: Command node exited with code 2 · at CustomBaseUpdater.spawnSyncLog <path>:<n>:<n>) · at main (<path>:<n>:<n>) …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 4.3.1 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 js-yaml.load sha256:9922ca80f240…go: <path> already existsgo · unclassified-diagnostic · outer go mod · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29Diagnostic re-verification candidate
-
observed PROJECT_TEST exit 1 ELIFECYCLE ×1 4.3.1 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 js-yaml.load sha256:7711694d48fa…ELIFECYCLE Test failed. See above for more details.javascript/test-runner · test-runner-diagnostic · outer pnpm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29
Showing the 12 most-reported of 14 recorded failure clusters. The rest are single reports.