babel-plugin-istanbul
A babel plugin that adds istanbul instrumentation to ES6 code
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): babel-plugin-istanbul is a coverage instrumentation tool; child_process usage is expected for tooling that may spawn processes for config loading or instrumentation. Stable false positive for this package. | ai | |
| dependencies | unvetted-dep:test-exclude | AI (dependencies): test-exclude is a canonical istanbuljs ecosystem package; expected dependency for this coverage plugin. | ai | |
| dependencies | unvetted-dep:@istanbuljs/schema | AI (dependencies): @istanbuljs/schema is a canonical istanbuljs ecosystem package; expected dependency for this coverage plugin. | ai | |
| dependencies | unvetted-dep:istanbul-lib-instrument | AI (dependencies): istanbul-lib-instrument is the core instrumentation library from the istanbuljs org; expected dependency for this coverage plugin. | ai | |
| dependencies | unvetted-dep:@istanbuljs/load-nyc-config | AI (dependencies): @istanbuljs/load-nyc-config is a canonical istanbuljs ecosystem package; expected dependency for this coverage plugin. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 8.0.2 | 5 / 12 | |
| 8.0.1 | 5 / 12 | |
| 8.0.0 | 5 / 12 | |
| 7.0.1 | 5 / 12 | |
| 7.0.0 | 5 / 12 | |
| 6.1.1 | 5 / 11 |
v8.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.