Recordsnpmlibnpmpublish10.0.2
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
| debian glibc | ubuntu glibc | |
|---|---|---|
| libnpmpublish.publish | 100%2 | 100%4 |
| libnpmpublish.unpublish | ||
| publish | 100%4 | 100%4 |
| unpublish | 100%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
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 2✓ — Verified: CONTRACT 1✓
|
LOW | 4 +2 | 1 | 100% | 1 · 1✓ | 2026-10-21 |
| node 22 · JS · npm · linux glibc · docker
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 4✓ — Verified: CONTRACT 3✓
|
MEDIUM | 4 +4 | 3 | 100% | 2 · 1✓ | 2026-10-21 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_TEST 5✓ — Usage: USED 6✓
|
LOW | 5 +6 | 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 5✓ · PROJECT_TEST 3✓ — Usage: USED 10✓ — Verified: UNKNOWN 0✓ 2✕
|
LOW | 8 +10 | 2 | 80% | 1 | 2026-10-21 |
Recent failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×1 10.0.2 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 libnpmpublish.unpublish sha256:a151e40a7605…<url> · import { unpublish } from <str> · ^^^^^^^^^ …npm · unclassified-diagnostic · outer npm test · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-21 · Last seen: 2026-10-21Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 10.0.2 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 libnpmpublish.publish sha256:ee5608aaa796…<url> · import { publish, unpublish } from <str>; · ^^^^^^^^^ …npm · unclassified-diagnostic · outer npm test · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-21 · Last seen: 2026-10-21Diagnostic re-verification candidate
Symbols
Published samples
- libnpmpublish 10.0.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. HOW MIT-0 · 2026-10-21