Recordsnpmbin-links5.0.0
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
| debian glibc | ubuntu glibc | |
|---|---|---|
| bin-links.checkBins | 100%2 | 100%2 |
| bin-links.getPaths | 100%2 | 100%1 |
| bin-links.resetSeen | 100%2 | 100%3 |
| binLinks | 100%2 | |
| binLinks.checkBins | 100%2 | |
| binLinks.getPaths | 100%2 |
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.
- 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 glibc · docker
Usage: USED 2✓
|
LOW | 0 +2 | 0 | — | 1 | 2026-10-20 |
| node 22 · JS · npm · linux glibc · docker
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 5✓ — Verified: CONTRACT 4✓
|
MEDIUM | 4 +5 | 4 | 100% | 2 · 1✓ | 2026-10-21 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_TEST 6✓ — Usage: USED 8✓
|
LOW | 6 +8 | 0 | 100% | 1 | 2026-10-20 |
| node 22.23 · JS · yarn · linux glibc
Observations: PROJECT_PROCESS 3✓
|
LOW | 3 | 0 | 100% | 1 | 2026-09-07 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 9✓ · PROJECT_TEST 6✓ 1✕ — Usage: USED 20✓ — Verified: UNKNOWN 0✓ 1✕
|
LOW | 16 +20 | 1 | 88% | 1 | 2026-10-21 |
Recent failure clusters
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×2 5.0.0 → 6.0.2 executionContext=node · os=linux · runtime=node@22.23 sha256:986d98189e70…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 2 · First recorded: 2026-09-14 · Last seen: 2026-10-20Diagnostic re-verification candidate
-
observed PROJECT_TEST exit 1 ERR_ASSERTION ×1 5.0.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:4904e63e5296…AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: · + actual - expected · + <str> · - <str>javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-20 · Last seen: 2026-10-20
Symbols
- binLinks 1 1 of 1 runs passed
- binLinks.checkBins 2 1 of 1 runs passed
- binLinks.getPaths 2 1 of 1 runs passed
- binLinks.resetSeen 2 1 of 1 runs passed