CodeSampleX

Recordsnpmmarked18.0.6

Which symbol ran where

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

2 12026-08-17
alpine musl11
marked.marked 100%4
marked.parse

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 musl · docker
Observations: PROJECT_LOAD 3✓ · PROJECT_TEST 3✓ — Usage: USED 3✓ — Verified: CONTRACT 3✓
HIGH 6 +3 3 100% 1 · 3✓ 2026-08-30
node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 1✓
LOW 1 0 100% 1 2026-08-17
node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 3✓
LOW 3 0 100% 1 2026-08-17

Symbols