Recordsnpmesbuild0.25.0
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
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.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
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 1✓ · PROJECT_TEST 1✓ — Usage: USED 1✓ — Verified: CONTRACT 1✓
|
LOW | 2 +1 | 1 | 100% | 1 · 1✓ | 2026-08-30 |
Symbols
- build 1 shared ×2 1 of 1 runs passed
- transformSync 1 shared ×3 1 of 1 runs passed
- version 1