babel-plugin-transform-es2015-modules-umd
This plugin transforms ES2015 modules to UMD
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): hzoo and amasad are both known Babel core team members; publisher rotation within the Babel org is expected. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2016, before Sigstore provenance existed. Stable for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Babel monorepo publishes many similarly-named plugins; tiny payload is normal for a single transform plugin. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 6.24.1 | 3 / 1 | |
| 6.24.0 | 3 / 1 | |
| 6.23.0 | 3 / 1 | |
| 6.22.0 | 3 / 1 | |
| 6.18.0 | 3 / 1 | |
| 6.12.0 | 3 / 1 | |
| 6.8.0 | 3 / 1 | |
| 6.6.5 | 3 / 1 | |
| 6.6.0 | 3 / 1 | |
| 6.5.0 | 3 / 1 | |
| 6.4.3 | 3 / 1 | |
| 6.4.0 | 3 / 1 | |
| 6.3.13 | 3 / 1 | |
| 6.2.4 | 3 / 1 | |
| 6.1.18 | 3 / 1 | |
| 6.1.17 | 3 / 1 | |
| 6.1.5 | 3 / 1 | |
| 6.1.4 | 3 / 1 | |
| 6.0.15 | 3 / 0 | |
| 6.0.14 | 3 / 0 | |
| 6.0.2 | 3 / 0 |
v6.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.24.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-03-13. This could indicate a legitimate maintainer transition or an account compromise.
v6.23.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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.4.3
2 findingsThis version was published by a different npm account than previous versions on 2016-01-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] 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.
v6.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.