babel-plugin-transform-export-extensions MIT 11 versions

babel-plugin-transform-export-extensions

npm Repository

Compile export extensions to ES2015

11

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

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): sebmck→hzoo is the well-known Babel maintainer transition (Sebastian McKenzie to Henry Zhu); stable for all babel-plugin-* packages.	ai	2026/04/24
bogus-package	bogus-package	AI (bogus-package): Tiny payload and templated names are normal for single-purpose Babel plugins in the monorepo.	ai	2026/04/24
phantom-deps	phantom-dep:babel-runtime	AI (phantom-deps): babel-runtime is a declared dependency used indirectly via Babel's transform pipeline; stable false positive.	ai	2026/04/24

Versions (showing 11 of 11)

Version	Deps	Published
6.22.0	2 / 1	2017-01-20
6.8.0	2 / 1	2016-05-02
6.5.0	2 / 1	2016-02-07
6.4.0	2 / 1	2016-01-06
6.3.13	2 / 1	2015-12-04
6.2.4	2 / 1	2015-11-25
6.1.18	2 / 1	2015-11-12
6.1.17	2 / 1	2015-11-12
6.1.4	2 / 1	2015-11-11
6.0.14	2 / 0	2015-10-30
6.0.2	2 / 0	2015-10-29

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

1 finding

LOW No provenance attestation provenance

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

v6.4.0

2 findings

HIGH Publisher changed: sebmck → hzoo (on 2016-01-06) provenance

This version was published by a different npm account than previous versions on 2016-01-06. 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

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.