← Home

@babel/plugin-syntax-numeric-separator

Allow parsing of Decimal, Binary, Hex and Octal literals that contain a Numeric Literal Separator

7
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

danezexistentialismhzoojlhwungloganfsmythnicolo-ribaudo

Keywords

babel-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Babel monorepo publishes hundreds of templated plugin packages; tiny payload, mass production, and inflated semver are all expected characteristics of @babel/* plugins. Not indicative of spam or malice. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance adoption on npm; absence of attestation is expected for this vintage of Babel plugin. 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

1 finding
INFO No provenance attestation provenance

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

v7.8.3

1 finding
INFO No provenance attestation provenance

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

v7.8.0

1 finding
INFO No provenance attestation provenance

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

v7.7.4

1 finding
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

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