istanbul-api BSD-3-Clause 43 versions

istanbul-api

npm Repository Homepage

High level API for istanbul features

43

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.

Maintainers

bcoecoreyfarrellgotwarlost

Keywords

istanbulapi

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Legitimate maintainer transition within istanbuljs org; coreyfarrell is a known contributor.	ai	2026/05/20
maintainer-change	maintainer-added	AI (maintainer-change): coreyfarrell is a known istanbuljs maintainer with strong track record.	ai	2026/05/20
dependencies	unvetted-dep:istanbul-lib-source-maps	AI (dependencies): istanbul-lib-source-maps is a first-party package in the same istanbuljs monorepo; this dependency is expected and legitimate for all versions of istanbul-api.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require in index.js loads istanbul's own sub-packages (istanbul-lib-*) via a controlled string pattern — a stable, intentional design in the istanbul ecosystem.	ai	2026/04/23
phantom-deps	phantom-dep:semver	AI (phantom-deps): semver is declared as a runtime dep and used in lib/ files; not imported in index.js but legitimately used within the package.	ai	2026/04/23

Versions (showing 43 of 43)

Version	Deps	Published
3.0.0	14 / 5	2019-05-10
2.1.7	13 / 0	2019-05-02
2.1.6	13 / 0	2019-04-24
2.1.5	13 / 0	2019-04-17
2.1.4	13 / 0	2019-04-09
2.1.3	13 / 0	2019-04-03
2.1.2	13 / 0	2019-03-12
2.1.1	13 / 0	2019-02-14
2.1.0	13 / 0	2019-01-26
2.0.8	12 / 5	2018-12-25
2.0.7	12 / 6	2018-12-19
2.0.6	12 / 6	2018-09-06
2.0.5	12 / 6	2018-07-24
2.0.4	12 / 6	2018-07-07
2.0.3	12 / 6	2018-06-27
2.0.2	12 / 6	2018-06-26
2.0.1	12 / 6	2018-06-06
2.0.0	12 / 6	2018-06-06
1.3.7	11 / 6	2018-09-05
1.3.6	12 / 6	2018-05-31
1.3.5	12 / 6	2018-05-31
1.3.4	12 / 6	2018-05-31
1.3.3	12 / 6	2018-05-31
1.3.2	12 / 6	2018-04-17
1.3.1	12 / 6	2018-03-09
1.3.0	12 / 6	2018-03-04
1.2.2	11 / 6	2018-02-13
1.2.1	11 / 6	2017-10-22
1.2.0	11 / 6	2017-10-21
1.1.14	11 / 6	2017-09-05
1.1.13	11 / 6	2017-08-26
1.1.12	11 / 6	2017-08-23
1.1.11	11 / 6	2017-07-16
1.1.10	11 / 6	2017-06-25
1.1.9	11 / 6	2017-05-27
1.1.8	11 / 6	2017-04-29
1.1.7	11 / 5	2017-03-27
1.1.6	11 / 5	2017-03-22
1.1.5	11 / 5	2017-03-21
1.1.4	11 / 5	2017-03-21
1.1.3	11 / 5	2017-03-21
1.1.1	11 / 8	2017-01-17
1.1.0	11 / 8	2016-12-27

v3.0.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: coreyfarrell.

LOW No provenance attestation provenance

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

v2.1.7

1 finding

LOW No provenance attestation provenance

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

v2.1.6

1 finding

LOW No provenance attestation provenance

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

v2.1.5

1 finding

LOW No provenance attestation provenance

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

v2.1.4

1 finding

LOW No provenance attestation provenance

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

v2.1.3

1 finding

LOW No provenance attestation provenance

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

v2.1.2

1 finding

LOW No provenance attestation provenance

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

v2.1.1

1 finding

LOW No provenance attestation provenance

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

v2.1.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.8

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.7

2 findings

HIGH Publisher changed: coreyfarrell → bcoe (on 2018-12-19) provenance

This version was published by a different npm account than previous versions on 2018-12-19. 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.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

2 findings

HIGH Publisher changed: bcoe → coreyfarrell (on 2018-07-24) provenance

This version was published by a different npm account than previous versions on 2018-07-24. 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.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

1 finding

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.