CodeSampleX

Recordsnpm@babel/helper-validator-identifier8.0.4

Which symbol ran where

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

62026-08-20
alpine muslubuntu glibc
@babel/helper-validator-identifier.isIdentifierChar 100%1
@babel/helper-validator-identifier.isIdentifierName 100%1
@babel/helper-validator-identifier.isIdentifierStart 100%1
@babel/helper-validator-identifier.isKeyword 100%1
@babel/helper-validator-identifier.isReservedWord 100%1
@babel/helper-validator-identifier.isStrictBindReservedWord 100%1

Showing the environments with the most evidence.

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 ◆ mark says one thing only: this network ran its own contract in THIS environment and it came back clean. Whether code exists for the release and API is a separate mark and a separate fact, because a sample does not stop existing when you switch the OS filter.

Code availability is a fact about this release and this API. It does not change with OS, runtime or package manager — whether it was verified HERE is the separate mark beside it.

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
Verified: CONTRACT 8✓
LOW 0 8 100% 0 · 1✓ 2026-08-20
node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 12✓
LOW 12 0 100% 1 2026-08-20
node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 2✓
LOW 2 0 100% 1 2026-08-20

Symbols

Published samples