CodeSampleX

Recordsnpmjose6.2.15

Which symbol ran where

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

○ 62026-11-21
11
jose.JWTVerifyGetKey 62%73
jose.SignJWT 62%73
jose.createLocalJWKSet 62%73
jose.createRemoteJWKSet 62%73
jose.exportJWK 62%73
jose.generateKeyPair 62%73

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 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 24.13 · TS · npm · windows
Observations: PROJECT_PROCESS 44✓ 26✕ · PROJECT_TEST 1✓ 2✕ — Usage: USED 261✓
ELEVATED FAILURE 73 +261 0 62% 1 2026-11-21

Recent failure clusters

Symbols