Recordsnpmverror1.10.1
Change the conditions
Current conditions
verror @1.10.1ubuntu glibc · x64 · node 22 · npm 10 · node
package-level total, not an API
0 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed
- Project observations
- 23 / 23
- Contract verifications
- 0 / 1
- Usage records
- 1
- Independent reporting peers
- 3
- Last recorded
- 2026-09-06
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 1 ·
Steady 3
First observed break
1.10.1
windows · node@24.13 · moduleSystem=cjs · executionContext=node
3 FAIL
· stage: UNKNOWN
· fingerprint: sha256:c113861ea6575a55f8e3a44f91634852da7cbcd3825a7f52264c417b812b7599
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| assert-plus | 1.0.0 | PASS All observations passed | contract passed | 19 project-days |
| core-util-is | 1.0.2 | PASS All observations passed | contract passed | 18 project-days |
| extsprintf | 1.4.1 | PASS All observations passed | contract passed | 18 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 UNKNOWN exit 1 Evidence gap ×1 1.10.1 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:795cbb5ee086…Error: Cannot find module <str> · Require stack: · - <path> · - <path>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30Diagnostic re-verification candidate