CodeSampleX

Recordsnpmistanbul-lib-source-maps5.0.6

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

Current conditions

istanbul-lib-source-maps @5.0.6ubuntu 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

Dependencies

LibraryVersionMeasured thereProjects
@jridgewell/trace-mapping 0.3.31 contract passed 2 project-days
debug 4.4.3 contract passed 2 project-days
istanbul-lib-coverage 3.2.2 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.

Library5.0.64.0.1
@jridgewell/trace-mapping 0.3.31
debug 4.4.3 4.4.3
istanbul-lib-coverage 3.2.2 3.2.2
source-map 0.6.1

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