Recordsnpmms2.0.0
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 musl · docker
Verified: CONTRACT 1✓
|
LOW | 0 | 1 | 100% | 0 · 1✓ | 2026-08-27 |
| node 22 · JS · npm · linux musl · docker
Verified: CONTRACT 1✓
|
LOW | 0 | 1 | 100% | 0 · 1✓ | 2026-08-20 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 1✓
|
LOW | 1 | 0 | 100% | 1 | 2026-08-27 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 3✓ 2✕
|
ELEVATED FAILURE | 5 | 0 | 60% | 1 | 2026-08-26 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 12✓
|
LOW | 12 | 0 | 100% | 1 | 2026-08-17 |
Recent failure clusters
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×43 2.0.0 → 2.1.3 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-13 · Last seen: 2026-08-27Diagnostic re-verification candidate
Symbols
- ms 1 1 of 1 runs passed
Published samples
- verify pkg:npm/ms@2.0.0 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. HOWnode 22.23.2 MIT-0 · 2026-08-20