babel-preset-stage-2
Babel preset for stage 2 plugins
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
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 from sebmck (Babel creator) to hzoo (long-time Babel core maintainer). Well-documented handoff. | ai | |
| provenance | no-provenance | AI (provenance): Package published in 2016, predates Sigstore provenance support. Expected for legacy Babel packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): babel-preset-stage-2 is a legitimate Babel monorepo package. Mass-production flag reflects Babel's many similarly-named packages; tiny payload and no keywords are expected for a preset aggregator. | ai | |
| phantom-deps | phantom-dep:babel-plugin-transform-async-generator-functions | AI (phantom-deps): Babel presets reference plugins by name in config objects rather than via require/import; this is the standard pattern for all Babel presets and not a phantom dependency concern. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 6.22.0 | 4 / 0 | |
| 6.18.0 | 4 / 0 | |
| 6.17.0 | 3 / 0 | |
| 6.16.0 | 5 / 0 | |
| 6.13.0 | 4 / 0 | |
| 6.11.0 | 2 / 0 | |
| 6.5.0 | 3 / 0 | |
| 6.3.13 | 3 / 0 | |
| 6.2.4 | 3 / 0 | |
| 6.1.18 | 3 / 0 | |
| 6.1.17 | 3 / 0 | |
| 6.1.2 | 3 / 0 | |
| 6.0.15 | 3 / 0 | |
| 6.0.14 | 3 / 0 |
v6.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.4
1 findingPackage 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.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.