← Home

istanbul-lib-hook

npm Repository Homepage

Hooks for require, vm and script used in istanbul

20
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 gitHead linked

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

bcoecoreyfarrellgotwarlost

Keywords

istanbulhook

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from coreyfarrell to bcoe is a documented legitimate maintainer transition within the istanbuljs org; bcoe is a well-known, trusted npm publisher. ai

Versions (showing 20 of 20)

Version Deps Published
3.0.0 1 / 3
2.0.7 1 / 0
2.0.6 1 / 0
2.0.5 1 / 0
2.0.4 1 / 0
2.0.3 1 / 0
2.0.2 1 / 2
2.0.1 1 / 3
2.0.0 1 / 3
1.2.2 1 / 3
1.2.1 1 / 3
1.2.0 1 / 3
1.1.0 1 / 3
1.0.7 1 / 3
1.0.6 1 / 3
1.0.5 1 / 3
1.0.4 1 / 3
1.0.3 1 / 3
1.0.2 1 / 3
1.0.0 1 / 6

v3.0.0

1 finding
LOW No provenance attestation provenance

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

v2.0.7

1 finding
LOW No provenance attestation provenance

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

v2.0.6

1 finding
LOW No provenance attestation provenance

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

v2.0.5

1 finding
LOW No provenance attestation provenance

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

v2.0.4

1 finding
LOW No provenance attestation provenance

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

v2.0.3

1 finding
LOW No provenance attestation provenance

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

v2.0.2

2 findings
HIGH Publisher changed: coreyfarrell → bcoe (on 2018-12-25) provenance

This version was published by a different npm account than previous versions on 2018-12-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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