@babel/plugin-syntax-export-namespace-from
Allow parsing of export namespace from
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Babel monorepo packages are intentionally tiny, templated, and versioned in lockstep with the monorepo semver. All three signals are structural false positives for @babel/* packages. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance on npm (published 2290 days ago); absence of provenance is expected for this era of Babel releases. | ai |
Versions (showing 6 of 6)
| 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 | |
| 7.0.0-beta.46 | 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. 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.
v7.0.0-beta.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.