Recordsnpmsocks2.8.7
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
| debian glibc | ubuntu glibc | |
|---|---|---|
| SocksClient | 100%2 | 100%3 |
| socks.SocksClient | 100%1 | 100%3 |
| socks.SocksClientError | 100%3 |
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 1✓
|
LOW | 0 +1 | 0 | — | 1 | 2026-09-14 |
| node 22 · JS · npm · linux glibc · docker
Observations: PROJECT_LOAD 1✓ · PROJECT_TEST 1✓ — Usage: USED 3✓ — Verified: CONTRACT 2✓
|
LOW | 2 +3 | 2 | 100% | 1 · 1✓ | 2026-10-17 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_TEST 1✓ — Usage: USED 1✓
|
LOW | 1 +1 | 0 | 100% | 1 | 2026-10-17 |
| 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 1✓ · PROJECT_TEST 2✓ — Usage: USED 3✓ — Verified: UNKNOWN 0✓ 1✕
|
LOW | 3 +3 | 1 | 75% | 1 | 2026-10-17 |
Recent failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×1 2.8.7 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 socks.SocksClient sha256:eaedb90db10c…<path>:<n> · this.emit(<str>, new util_1.SocksClientError(err, this.options)); · ^ · SocksClientError: Socks5 proxy rejected connection - Failurenpm · unclassified-diagnostic · outer npm test · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-17 · Last seen: 2026-10-17Diagnostic re-verification candidate
Symbols
- socks.SocksClient 2 1 of 2 runs passed
- socks.SocksClientError 0 of 1 runs passed