@babel/plugin-syntax-dynamic-import
Allow parsing of import()
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): nicolo-ribaudo is a well-known Babel core team member; this is a legitimate maintainer transition within the Babel project, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): nicolo-ribaudo is a long-standing Babel core contributor with extensive track record; addition is a legitimate team transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of xtuc is part of a legitimate Babel team restructuring, not a takeover indicator. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Tiny payload is expected for a syntax-only Babel plugin. Spam-flagged prior maintainers (hzoo, loganfsmyth, danez) are well-known Babel contributors — false positive from spam detection. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2018, predating Sigstore provenance attestations. Not a meaningful risk signal for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 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.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
2 findingsThis version was published by a different npm account than previous versions on 2018-12-03. 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.
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.