CodeSampleX

Recordsnpmminimatch10.1.1

Which symbol ran where

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

6 122026-08-20
alpine muslubuntu glibc11
minimatch 100%4 100%11
minimatch.Minimatch 100%4 100%2
minimatch.escape 100%4 100%4
minimatch.filter 100%4 100%5
minimatch.minimatch 100%4 100%11
minimatch.unescape 100%4 100%4

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 22 · JS · npm · linux musl · docker
Observations: PROJECT_LOAD 5✓ · PROJECT_TEST 5✓ — Usage: USED 5✓ — Verified: CONTRACT 14✓
HIGH 10 +5 14 100% 2 · 3✓ 2026-08-30
node 22 · JS · npm · linux musl · docker
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 2✓ — Verified: CONTRACT 2✓
MEDIUM 4 +2 2 100% 2 · 2✓ 2026-08-30
node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 4✓
LOW 4 0 100% 1 2026-08-20
node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 11✓
LOW 11 0 100% 1 2026-08-18

Symbols

Published samples