babel-helper-optimise-call-expression MIT 24 versions

babel-helper-optimise-call-expression

npm Repository

Helper function to optimise call expression

24

Versions

MIT

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

amasadhzoojmmloganfsmythsebmckthejameskyle

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Both loganfsmyth and hzoo are known Babel core maintainers; this is a routine team rotation, not a suspicious takeover.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): Flagged maintainers are legitimate Babel core team members; tiny payload is expected for a focused helper utility; no-keywords is cosmetic.	ai	2026/04/23
phantom-deps	phantom-dep:babel-runtime	AI (phantom-deps): babel-runtime as a phantom dep is a standard Babel 6 pattern; used transitively for polyfills, not a security concern.	ai	2026/04/23

Versions (showing 24 of 24)

Version	Deps	Published
6.24.1	2 / 0	2017-04-07
6.23.0	2 / 0	2017-02-14
6.22.0	2 / 0	2017-01-20
6.18.0	2 / 0	2016-10-24
6.8.0	2 / 0	2016-05-02
6.6.0	2 / 0	2016-02-29
6.5.0	2 / 0	2016-02-07
6.3.13	2 / 0	2015-12-04
6.2.4	2 / 0	2015-11-25
6.1.18	2 / 0	2015-11-12
6.1.17	2 / 0	2015-11-12
6.1.16	2 / 0	2015-11-12
6.1.13	2 / 0	2015-11-12
6.1.12	2 / 0	2015-11-12
6.1.10	2 / 0	2015-11-12
6.1.9	2 / 0	2015-11-12
6.1.8	2 / 0	2015-11-12
6.1.7	2 / 0	2015-11-12
6.1.6	2 / 0	2015-11-12
6.1.5	2 / 0	2015-11-12
6.0.15	2 / 0	2015-11-01
6.0.14	2 / 0	2015-10-30
6.0.2	2 / 0	2015-10-29
6.0.0	2 / 0	2015-10-29

v6.24.1

2 findings

HIGH Publisher changed: loganfsmyth → hzoo (on 2017-04-07) provenance

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

v6.23.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: hzoo → loganfsmyth (on 2017-02-14) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-02-14. This could indicate a legitimate maintainer transition or an account compromise.

v6.22.0

1 finding

LOW No provenance attestation provenance

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

v6.18.0

1 finding

LOW No provenance attestation provenance

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

v6.8.0

1 finding

LOW No provenance attestation provenance

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

v6.6.0

1 finding

LOW No provenance attestation provenance

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

v6.5.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: sebmck → hzoo (on 2016-02-07) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-02-07. This could indicate a legitimate maintainer transition or an account compromise.

v6.3.13

1 finding

LOW No provenance attestation provenance

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

v6.2.4

1 finding

LOW No provenance attestation provenance

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

v6.1.18

1 finding

LOW No provenance attestation provenance

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

v6.1.17

1 finding

LOW No provenance attestation provenance

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

v6.1.16

1 finding

LOW No provenance attestation provenance

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

v6.1.13

1 finding

LOW No provenance attestation provenance

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

v6.1.12

1 finding

LOW No provenance attestation provenance

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

v6.1.10

1 finding

LOW No provenance attestation provenance

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

v6.1.9

1 finding

LOW No provenance attestation provenance

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

v6.1.8

1 finding

LOW No provenance attestation provenance

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

v6.1.7

1 finding

LOW No provenance attestation provenance

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

v6.1.6

1 finding

LOW No provenance attestation provenance

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

v6.1.5

1 finding

LOW No provenance attestation provenance

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

v6.0.15

1 finding

LOW No provenance attestation provenance

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

v6.0.14

1 finding

LOW No provenance attestation provenance

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

v6.0.2

1 finding

LOW No provenance attestation provenance

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

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.