Recordsnpmbabel-plugin-istanbul6.1.1
Change the conditions
Current conditions
babel-plugin-istanbul @6.1.1alpine musl · x64 · node 22 · npm · node
package-level total, not an API
1 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 came back clean (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-30
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @babel/helper-plugin-utils | 7.29.7 | contract passed | 6 project-days |
| @istanbuljs/load-nyc-config | 1.1.0 | contract passed | 6 project-days |
| @istanbuljs/schema | 0.1.6 | contract passed | 6 project-days |
| istanbul-lib-instrument | 5.2.1 | contract passed | 6 project-days |
| test-exclude | 6.0.0 | 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.
| Library | 7.0.1 | 6.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
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×2 6.1.1 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:986d98189e70…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 6.1.1 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:83bb774d0366…<path>:<n> · const snapshotsAdded = snapshotResults.added; · ^ · TypeError: Cannot read properties of undefined (reading <str>)node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 6.1.1 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:91ad26545eb1…node:internal/modules/cjs/loader:<n> · throw err; · ^ · Error: Cannot find module <str>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 6.1.1 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:eb0938a47430…node:assert:<n> · throw new AssertionError(obj); · ^ · AssertionError [ERR_ASSERTION]: jest.getVersion() should return 29.6.3node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate