← Home

babel-helper-is-void-0

npm Repository Homepage

## Installation

9
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

babeljsboopathihzoologanfsmythvignesh.shanmugam

Keywords

babel-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-takeover AI (maintainer-change): Legitimate transfer from amasad to Babel core team (hzoo, boopathi, vignesh.shanmugam) — well-documented project handoff within the Babel org. ai
provenance publisher-changed AI (provenance): Publisher change from amasad to boopathi reflects the documented babili/babel-minify project transfer to the Babel team. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers are established Babel core team members; legitimate org transfer. ai
maintainer-change maintainer-removed AI (maintainer-change): amasad (Amjad Masad) handed off the project to the Babel team; removal is expected. ai

Versions (showing 9 of 9)

Version Deps Published
0.4.3 0 / 0
0.4.2 0 / 0
0.4.1 0 / 0
0.4.0 0 / 0
0.3.0 0 / 0
0.2.0 0 / 0
0.1.1 0 / 0
0.1.0 0 / 0
0.0.1 0 / 0

v0.4.3

1 finding
LOW No provenance attestation provenance

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

v0.4.2

1 finding
LOW No provenance attestation provenance

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

v0.4.1

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.1

3 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (amasad) were replaced by new maintainers (vignesh.shanmugam, hzoo, boopathi). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: amasad → boopathi (on 2017-05-22) provenance

This version was published by a different npm account than previous versions on 2017-05-22. 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.

v0.1.0

3 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (amasad) were replaced by new maintainers (vignesh.shanmugam, hzoo, boopathi). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: amasad → boopathi (on 2017-05-22) provenance

This version was published by a different npm account than previous versions on 2017-05-22. 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.

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