CodeSampleX

Recordsnpmcaniuse-lite1.0.30001809

Which symbol ran where

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

42026-08-30
alpine musldebian glibcubuntu glibc11
caniuse-lite.agents 100%1
caniuse-lite.feature 100%1
caniuse-lite.features 100%1
caniuse-lite.region 100%1

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 · JS · pnpm · windows
Usage: USED 1✓
LOW 0 +1 0 — 1 2026-09-01
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 · JS · npm · linux glibc · docker
Observations: PROJECT_LOAD 1✓ · PROJECT_TEST 1✓ — Usage: USED 2✓ — Verified: CONTRACT 1✓
LOW 2 +2 1 100% 1 · 1✓ 2026-09-07
node 22.16 · JS · pnpm · windows
Observations: PROJECT_COMPILE 5✓ · PROJECT_PROCESS 1✓ · PROJECT_TEST 5✓ 3✕ — Usage: USED 72✓
LOW 14 +72 0 79% 1 2026-08-23
node 22.16 · TS · npm · windows
Observations: PROJECT_COMPILE 1✓ · PROJECT_TEST 9✓ · PROJECT_TYPECHECK 1✓ 1✕ — Usage: USED 5✓
LOW 12 +5 0 92% 1 2026-08-24
node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 28✓ 8✕ — Usage: USED 11✓
MEDIUM 36 +11 0 78% 2 2026-08-30
node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 26✓ 4✕ · PROJECT_TEST 1✓ — Verified: UNKNOWN 0✓ 1✕
MEDIUM 31 1 84% 2 2026-08-30
node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 3✓
LOW 3 0 100% 1 2026-08-18
node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 31✓ · PROJECT_TEST 1✓ — Usage: USED 1✓
LOW 32 +1 0 100% 1 2026-08-18
node 24.13 · TS · pnpm · windows
Observations: PROJECT_COMPILE 17✓ · PROJECT_TEST 15✓ 2✕ — Usage: USED 2✓
LOW 34 +2 0 94% 1 2026-09-01
node 24.13 · TS · npm · windows
Observations: PROJECT_COMPILE 24✓ 12✕ · PROJECT_TEST 50✓ 11✕ — Usage: USED 35✓ — Verified: UNKNOWN 0✓ 12✕
ELEVATED FAILURE 97 +35 12 68% 1 2026-09-13
node 24.13 · JS · pnpm · windows
Observations: PROJECT_COMPILE 126✓ 74✕ · PROJECT_TEST 161✓ 17✕ — Usage: USED 1,198✓ — Verified: PROCESS_START 0✓ 2✕ · UNKNOWN 0✓ 218✕
ELEVATED FAILURE 378 +1198 220 48% 1 2026-09-16

Verification frontier

What the signed receipts establish about moving off this release. Each line holds only under the conditions it names; nothing is inferred between measured releases, and a measured boundary is never shown as an inferred candidate.

Recent failure clusters

Showing the 12 most-reported of 227 recorded failure clusters. The rest are single reports.

Symbols

Published samples