Recordsnpmnpm-package-arg12.0.2
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
| debian glibc | ubuntu glibc | |
|---|---|---|
| Result | 100%2 | |
| npa | 100%2 | |
| npa.resolve | 100%2 | |
| npa.toPurl | 100%2 | |
| npm-package-arg.resolve | 100%2 | 67%3 |
| npm-package-arg.toPurl | 50%2 |
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 3✓
|
LOW | 0 +3 | 0 | — | 1 | 2026-10-18 |
| node 22 · JS · npm · linux glibc · docker
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 3✓ — Verified: CONTRACT 2✓
|
LOW | 4 +3 | 2 | 100% | 1 · 1✓ | 2026-10-19 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 1✓ — Usage: USED 2✓
|
LOW | 1 +2 | 0 | 100% | 1 | 2026-10-18 |
| 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 2✓ · PROJECT_TEST 20✓ 2✕ — Usage: USED 22✓ — Verified: UNKNOWN 0✓ 2✕
|
LOW | 24 +22 | 2 | 85% | 1 | 2026-10-18 |
Recent failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×2 12.0.2 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:536db39a2e08…<path>:<n> · const closeError = new Error(<str>) · ^ · Error: command failednpm · unclassified-diagnostic · outer npm test · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-18 · Last seen: 2026-10-18Diagnostic re-verification candidate
-
observed PROJECT_TEST exit 1 ERR_ASSERTION ×1 12.0.2 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 npm-package-arg.resolve sha256:2c4eb57fcc76…AssertionError [ERR_ASSERTION]: Missing expected exception. · at <url> · at ModuleJob.run (node:internal/modules/esm/module_job:<n>:<n>) …javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-17 · Last seen: 2026-10-17
-
observed PROJECT_TEST exit 1 ERR_ASSERTION ×1 12.0.2 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:8c3539be02dd…AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal: · + actual - expected · Comparison { · + message: <str>,javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-18 · Last seen: 2026-10-18
Symbols
- Result 1 1 of 1 runs passed
- npa 1 1 of 1 runs passed
- npm-package-arg.resolve 2 1 of 1 runs passed
- npm-package-arg.toPurl 1