Recordsnpmwhy-is-node-running2.3.0
Change the conditions
Current conditions
why-is-node-running @2.3.0ubuntu glibc · x64 · node 22 · npm 10 · node
package-level total, not an API
0 of 5 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (1)
- Project observations
- 36 / 41
- Contract verifications
- 0 / 5
- Usage records
- 21
- Independent reporting peers
- 2
- Failures with a captured fingerprint
- 1 / 5
- Last recorded
- 2026-08-31
Evidence you can open
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| siginfo | 2.0.0 | contract passed | 8 project-days |
| stackback | 0.0.2 | contract passed | 8 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
Recent failure clusters
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×5 2.3.0 executionContext=node · moduleSystem=esmEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-14 · Last seen: 2026-08-30Diagnostic re-verification candidate
-
observed PROCESS_START process start failed Evidence gap ×1 2.3.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed PROJECT_TEST exit 1 ERR_LOAD_URL ×1 2.3.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:a60e7101af87…Contract test failed: Error: Failed to load custom Reporter from basic · at loadCustomReporterModule (fil<path>:<n>:<n>) · at fil<path>:<n>:<n> …javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31
-
observed UNKNOWN exit 1 Evidence gap ×1 2.3.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:72ba2d1e946f…<path>: No module named pippython3 · unclassified-diagnostic · outer python3 · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 2.3.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:91ad26545eb1…node:internal/modules/cjs/loader:<n> · throw err; · ^ · Error: Cannot find module <str>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 2.3.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:d7f5d491441c…Traceback (most recent call last): · File <str>, line 71, in <module> · AssertionError: is_annotated must return True for Annotated· unclassified-diagnostic · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 2.3.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:8fd30f2a6304…fil<path>:<n> · throw new Error(errorMsg); · ^ · Error: Vitest failed to access its internal state.node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate