← Home

@babel/plugin-syntax-bigint

Allow parsing of BigInt literals

7
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

danezdevelopitexistentialismhzoologanfsmythnicolo-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 package: templated naming, tiny payload, and inflated semver are all intentional patterns for the Babel plugin ecosystem. Not indicative of spam or malice. ai
provenance no-provenance AI (provenance): Package is ~2290 days old, predating npm provenance attestation. Absence is expected for packages of this age. ai

Versions (showing 7 of 7)

Version Deps Published
7.8.3 1 / 1
7.8.0 1 / 1
7.7.4 1 / 1
7.4.4 1 / 1
7.4.3 1 / 1
7.2.0 1 / 1
7.0.0 1 / 1

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.4.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.4.3

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.