Recordsnpmwhy-is-node-running2.3.0
Change the conditions
Current conditions
why-is-node-running @2.3.0windows 11 · x64 · node 22 · npm 11 · node
package-level total, not an API
13 of 14 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (1)
- Project observations
- 13 / 14
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 1
- Last recorded
- 2026-08-20
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 PROJECT_TYPECHECK Evidence gap ×2 2.3.0 executionContext=node · moduleSystem=cjs · os=windowsEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-20 · Last seen: 2026-08-21Diagnostic re-verification candidate