CodeSampleX

Recordsnpmnode-releases2.0.63

Which symbol ran where

Symbols × operating systems for this version. Cells drill into the package's compatibility cube.

3○ 52026-11-14
debian glibcubuntu glibc
node-releases.filter 100%2 100%4
node-releases.find 100%2
node-releases.json 100%2 100%3
node-releases.length 100%2 100%4
node-releases.slice 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.

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 glibc · docker
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 2✓ — Verified: CONTRACT 3✓
LOW 4 +2 3 100% 1 · 1✓ 2026-11-14
node 22 · JS · npm · linux glibc · docker
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 2✓ — Verified: CONTRACT 1✓
LOW 4 +2 1 100% 1 · 1✓ 2026-11-14
node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 1✓ — Usage: USED 1✓
LOW 1 +1 0 100% 1 2026-11-07
node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 6✓ · PROJECT_TEST 10✓ 1✕ — Usage: USED 17✓ — Verified: UNKNOWN 0✓ 1✕
LOW 17 +17 1 89% 1 2026-11-12

Recent failure clusters

Symbols

Published samples