Recordsnpmrouter2.2.0
Change the conditions
Current conditions
router @2.2.0ubuntu glibc · x64 · node 22 · npm 10 · node
package-level total, not an API
0 of 4 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
- 38 / 39
- Contract verifications
- 0 / 4
- Usage records
- 14
- Independent reporting peers
- 2
- Failures with a captured fingerprint
- 0 / 1
- Last recorded
- 2026-09-14
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 1 ·
Steady 5
First observed break
2.2.0
windows · node@24.13 · moduleSystem=esm · executionContext=node
32 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| debug | 4.4.3 | PASS All observations passed | contract passed | 26 project-days |
| depd | 2.0.0 | PASS All observations passed | contract passed | 26 project-days |
| is-promise | 4.0.0 | PASS All observations passed | contract passed | 26 project-days |
| parseurl | 1.3.3 | PASS All observations passed | contract passed | 26 project-days |
| path-to-regexp | 8.4.2 | PASS All observations passed | contract passed | 25 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_MODULE_NOT_FOUND Evidence gap ×13 2.2.0 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-13 · Last seen: 2026-08-21Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 2.2.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:10e769edac62…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value: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.2.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 ERR_ASSERTION Evidence gap ×1 2.2.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:986d98189e70…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: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.2.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:9be950af9140…Traceback (most recent call last): · File <str>, line 1, in <module> · ModuleNotFoundError: No module named <str>python3 · 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