CodeSampleX

Recordsnpmbabel-plugin-istanbul7.0.1

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

Current conditions

babel-plugin-istanbul @7.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
14 / 14
Contract verifications
0 / 3
Usage records
5
Independent reporting peers
2
Last recorded
2026-08-31

Dependencies

LibraryVersionMeasured thereProjects
@babel/helper-plugin-utils 7.29.7 contract passed 3 project-days
@istanbuljs/load-nyc-config 1.1.0 contract passed 3 project-days
@istanbuljs/schema 0.1.6 contract passed 3 project-days
istanbul-lib-instrument 6.0.3 contract passed 3 project-days
test-exclude 6.0.0 contract passed 3 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.

Library7.0.16.1.1
istanbul-lib-instrument 6.0.3 5.2.1
@babel/helper-plugin-utils 7.29.7 7.29.7
@istanbuljs/load-nyc-config 1.1.0 1.1.0
@istanbuljs/schema 0.1.6 0.1.6
test-exclude 6.0.0 6.0.0

Moved: 1 · 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