Recordsnpmxmlhttprequest-ssl2.1.2xmlhttprequest-ssl.XMLHttpRequest
OS × runtime at a glance
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 ◆ mark says one thing only: this network ran its own contract in THIS environment and it came back clean. Whether code exists for the release and API is a separate mark and a separate fact, because a sample does not stop existing when you switch the OS filter.
- there is sample code for this release and API, whatever the environment
- we ran our own contract in this environment and it came back clean
- our sample failed here
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
Code availability is a fact about this release and this API. It does not change with OS, runtime or package manager — whether it was verified HERE is the separate mark beside it.
Published samples
- verify xmlhttprequest-ssl.XMLHttpRequest in pkg:npm/xmlhttprequest-ssl@2.1.2 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWxmlhttprequest-ssl.XMLHttpRequestnode 22.23.2 MIT-0 · 2026-08-21
Compatibility matrix
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
Verified: CONTRACT 1✓
|
LOW | 0 | 1 | 100% | 0 · 1✓ | 2026-08-21 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 1✓
|
LOW | 1 | 0 | 100% | 1 | 2026-08-21 |
snapshot · 2026-08-26
Failure clusters
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×5 2.1.2 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-26 · Last seen: 2026-08-26Diagnostic re-verification candidate