istanbul-lib-instrument BSD-3-Clause 10 versions

istanbul-lib-instrument

npm Repository Homepage

Core istanbul API for JS code coverage

10

Versions

BSD-3-Clause

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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.

Keywords

coverageistanbuljsinstrumentation

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:semver	AI (phantom-deps): semver is declared in package.json dependencies and is legitimately used by Istanbul instrumentation; phantom-dep flag is a false positive for this package.	ai	2026/04/21
phantom-deps	phantom-dep:@babel/parser	AI (phantom-deps): @babel/parser is declared in package.json dependencies and is a core part of Istanbul's Babel-based instrumentation; loaded by framework convention as noted by the analyzer.	ai	2026/04/21

Versions (showing 10 of 10)

Version	Deps	Published
6.0.3	5 / 9	2024-06-30
6.0.2	5 / 9	2024-02-19
6.0.1	5 / 9	2023-10-04
6.0.0	5 / 9	2023-07-25
5.2.1	5 / 9	2022-10-05
5.2.0	5 / 9	2022-04-20
5.1.0	5 / 9	2021-10-27
5.0.4	5 / 9	2021-10-16
5.0.3	5 / 9	2021-10-06
5.0.2	5 / 9	2021-09-13

v6.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.