babel-plugin-syntax-class-constructor-call

Allow parsing of class constructor calls (deprecated)

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

Keywords

babel-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Legitimate transition from sebmck (Babel creator) to hzoo (Babel core maintainer); both are well-known Babel team members.	ai	2026/04/24
phantom-deps	phantom-dep:babel-runtime	AI (phantom-deps): babel-runtime is declared as a dependency and referenced in config/build output; benign for Babel plugins.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package published in 2016, predates Sigstore provenance support; stable for this package.	ai	2026/04/24

Versions (showing 21 of 21)

Version	Deps	Published
6.18.0	0 / 0	2016-10-24
6.13.0	0 / 0	2016-08-04
6.8.0	1 / 1	2016-05-02
6.5.0	1 / 1	2016-02-07
6.3.13	1 / 1	2015-12-04
6.2.4	1 / 1	2015-11-25
6.1.18	1 / 1	2015-11-12
6.1.17	1 / 1	2015-11-12
6.1.16	1 / 1	2015-11-12
6.1.13	1 / 1	2015-11-12
6.1.12	1 / 1	2015-11-12
6.1.10	1 / 1	2015-11-12
6.1.8	1 / 1	2015-11-12
6.1.7	1 / 1	2015-11-12
6.1.6	1 / 1	2015-11-12
6.1.5	1 / 1	2015-11-12
6.1.4	1 / 1	2015-11-11
6.0.15	1 / 0	2015-11-01
6.0.14	1 / 0	2015-10-30
6.0.12	1 / 0	2015-10-30
6.0.2	1 / 0	2015-10-29

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

1 finding

INFO No provenance attestation provenance

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

v6.8.0

1 finding

INFO No provenance attestation provenance

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

v6.5.0

2 findings

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

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.

LOW No provenance attestation provenance

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

v6.3.13

1 finding

INFO No provenance attestation provenance

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

v6.2.4

1 finding

INFO No provenance attestation provenance

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

v6.1.18

1 finding

INFO No provenance attestation provenance

[Accepted risk] 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

INFO No provenance attestation provenance

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

v6.1.12

1 finding

INFO No provenance attestation provenance

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

v6.1.10

1 finding

INFO No provenance attestation provenance

[Accepted risk] 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.1.4

1 finding

INFO No provenance attestation provenance

[Accepted risk] 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.12

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

INFO No provenance attestation provenance

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