Recordsnpmbare-signals5.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.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 13✓ 11✕ — Usage: USED 42✓
|
ELEVATED FAILURE | 24 +42 | 0 | 54% | 3 | 2026-08-27 |
Recent failure clusters
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×11 5.0.0 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-27Diagnostic re-verification candidate
Symbols
No symbols with evidence yet.
Published samples
- verify pkg:npm/bare-signals@5.0.0 signal handling and listeners 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-27