Recordsnpmtuf-js3.1.0
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
| debian glibc | ubuntu glibc | |
|---|---|---|
| BaseFetcher | 100%2 | 100%3 |
| TargetFile | 100%2 | 100%3 |
| Updater | 100%1 | 100%2 |
| tuf-js.BaseFetcher | 100%1 | 100%3 |
| tuf-js.TargetFile | 100%1 | 100%3 |
| tuf-js.Updater | 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 1✓ · PROJECT_TEST 1✓ — Usage: USED 3✓ — Verified: CONTRACT 1✓
|
LOW | 2 +3 | 1 | 100% | 1 · 1✓ | 2026-10-18 |
| 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-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 6✓ · PROJECT_TEST 13✓ 1✕ — Usage: USED 17✓ — Verified: UNKNOWN 0✓ 1✕
|
LOW | 20 +17 | 1 | 90% | 1 | 2026-10-18 |
Recent failure clusters
-
observed PROJECT_TEST exit 1 ERR_ASSERTION ×1 3.1.0 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
-
observed UNKNOWN exit 1 Evidence gap ×1 3.1.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:5cb8e084fdab…<path>:<n> · throw new error_1.UnsignedMetadataError(`${delegatedRole} was signed by ${signingKeys.size}/${role.threshold} keys`); · ^ …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-18 · Last seen: 2026-10-18Diagnostic re-verification candidate
Symbols
- tuf-js.BaseFetcher 2 1 of 1 runs passed
- tuf-js.TargetFile 2 1 of 1 runs passed
- tuf-js.Updater 1