CodeSampleX

Recordsnpmistanbul-lib-source-maps4.0.1

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

Current conditions

istanbul-lib-source-maps @4.0.1ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 3 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
9 / 9
Contract verifications
0 / 3
Usage records
1
Independent reporting peers
2
Last recorded
2026-09-02

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 3

First observed break

4.0.1

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

1 FAIL · stage: UNKNOWN · fingerprint: sha256:91ad26545eb1f3df29e3d9731c4244f3cf919942db2aa314b6b8d67ca84b47ef

Library Version Health Measured there Projects
debug 4.4.3 PASS All observations passed contract passed 6 project-days
istanbul-lib-coverage 3.2.2 PASS All observations passed contract passed 6 project-days
source-map 0.6.1 PASS All observations passed contract passed 6 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.

Moved: 0 · unchanged at every release: 4

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