← Home

babel-plugin-transform-exponentiation-operator

npm Repository

Compile exponentiation operator to ES5

11
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

amasadhzoojmmloganfsmythsebmckthejameskyle

Keywords

babel-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate maintainer transition from sebmck (Babel creator) to hzoo (long-time Babel core maintainer); well-documented project handoff. ai
provenance no-provenance AI (provenance): Published in 2016, before npm provenance/Sigstore existed. Expected for legacy Babel packages. ai
bogus-package bogus-package AI (bogus-package): Legitimate Babel monorepo plugin; spam-publisher and mass-production signals are false positives for the Babel core team. Tiny payload is expected for a focused transform plugin. ai
phantom-deps phantom-dep:babel-runtime AI (phantom-deps): babel-runtime is a standard indirect dependency in Babel 6 plugins; injected via helper transforms, not directly imported. Expected pattern for this package. ai

Versions (showing 11 of 11)

Version Deps Published
6.24.1 3 / 1
6.22.0 3 / 1
6.8.0 3 / 1
6.5.0 3 / 1
6.3.13 3 / 1
6.2.4 3 / 1
6.1.18 3 / 1
6.1.17 3 / 1
6.1.4 3 / 1
6.0.14 3 / 0
6.0.2 3 / 0

v6.24.1

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

Matched 3 signal(s), weighted score 7: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: jmm, sebmck, amasad, thejameskyle, hzoo, loganfsmyth. • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'loganfsmyth' owns 167 packages, ≥70% share a templated name shape. • [S_TINY_PAYLOAD] Tiny payload: 1 code file(s), 2448 bytes total.

LOW No provenance attestation provenance

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

v6.22.0

2 findings
HIGH Publisher changed: sebmck → hzoo (on 2017-01-20) provenance

This version was published by a different npm account than previous versions on 2017-01-20. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v6.8.0

2 findings
HIGH Publisher changed: sebmck → hzoo (on 2016-05-02) provenance

This version was published by a different npm account than previous versions on 2016-05-02. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v6.5.0

2 findings
HIGH Publisher changed: sebmck → hzoo (on 2016-02-07) provenance

This version was published by a different npm account than previous versions on 2016-02-07. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v6.3.13

1 finding
LOW No provenance attestation provenance

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

v6.2.4

1 finding
LOW No provenance attestation provenance

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

v6.1.18

1 finding
LOW No provenance attestation provenance

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

v6.1.17

1 finding
LOW No provenance attestation provenance

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

v6.1.4

1 finding
LOW No provenance attestation provenance

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

v6.0.14

1 finding
LOW No provenance attestation provenance

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

v6.0.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.