← Home

@babel/preset-modules

npm Repository Homepage

A Babel preset that targets modern browsers by fixing engine bugs.

9
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

hzooexistentialismnicolo-ribaudojlhwungdevelopit

Keywords

babelpresetpreset-envmodernmodulesES Modulesmodule/nomodule

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Babel core package; signals (tiny payload, no deps, no keywords) are normal for a v0.0.1 skeleton under @babel scope by trusted maintainer. ai
phantom-deps phantom-dep:@babel/types AI (phantom-deps): @babel/types is a standard Babel ecosystem dependency used by convention in Babel presets/plugins; phantom-dep finding is a stable false positive for this package. ai

Versions (showing 9 of 9)

Hide prereleases
Version Deps Published
0.1.6 5 / 28
0.1.5 5 / 28
0.1.4 5 / 28
0.1.3 5 / 28
0.1.2 5 / 28
0.1.1 5 / 28
0.1.0 5 / 28
0.0.1 0 / 0
0.1.6-no-external-plugins 3 / 28

v0.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1

2 findings
HIGH Low-value / spam package indicators (5 signals, score 7) bogus-package

Matched 5 signal(s), weighted score 7: • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'loganfsmyth' owns 167 packages, ≥70% share a templated name shape. • [S_DESC_MATCHES_NAME] Description is empty or just restates the package name. • [S_NO_KEYWORDS] No keywords declared. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared. • [S_TINY_PAYLOAD] Tiny payload: 0 code file(s), 344 bytes total.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.6-no-external-plugins

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.