@babel/plugin-syntax-import-meta
Allow parsing of import.meta
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 → nicolo-ribaudo is a well-documented Babel core team transition; both are long-standing maintainers. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): nicolo-ribaudo is a current Babel core maintainer; legitimate team change. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): xtuc removal is part of normal Babel team roster changes. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Official Babel monorepo package; templated names, tiny payload, and coordinated semver versioning are all expected characteristics of the Babel plugin ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): Established Babel package published before Sigstore provenance was widely adopted; absence is expected for this package's age. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 7.10.4 | 1 / 1 | |
| 7.10.1 | 1 / 1 | |
| 7.8.3 | 1 / 1 | |
| 7.8.0 | 1 / 1 | |
| 7.7.4 | 1 / 1 | |
| 7.2.0 | 1 / 1 | |
| 7.0.0 | 1 / 1 |
v7.10.1
2 findingsThis version was published by a different npm account than previous versions on 2020-05-27. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.3
2 findingsThis version was published by a different npm account than previous versions on 2020-01-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.