CodeSampleX

Recordsnpm@emnapi/runtime1.10.0

Change the conditions
Fixed
Runtimenode 22 Package version1.10.0
Filter OSubuntu glibc Symbolwhole package Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

@emnapi/runtime @1.10.0ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 2 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
4 / 4
Contract verifications
0 / 2
Independent reporting peers
1
Last recorded
2026-08-31
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 1

First observed break

1.10.0

linux · node@22.23 · moduleSystem=esm · executionContext=node

1 FAIL · stage: UNKNOWN · fingerprint: sha256:054c93088b95acdec26c27553355ea7447db339349572fdd4ba431478ecb744a

View exact conditions View failure cluster
Library Version Health Measured there Projects
tslib 2.8.1 PASS All observations passed contract passed 2 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.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Library1.11.31.11.11.10.01.7.1
tslib 2.8.1 2.8.1 2.8.1 2.8.1

Moved: 0 · unchanged at every release: 1

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.

Recent failure clusters