babel-helper-remove-or-void
## Installation
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): Legitimate transfer to Babel core team members (hzoo, boopathi, vignesh.shanmugam) within the babel/babili monorepo project. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed from amasad to boopathi as part of official Babel/babili project maintainer transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are established Babel core team members; legitimate project handoff. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): amasad stepped away from the project; removal is consistent with legitimate transition. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate Babel ecosystem helper from babel/minify monorepo. hzoo and loganfsmyth are known Babel core team members; tiny payload and no deps are expected for a focused helper utility. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package (3527 days old) predating Sigstore provenance; no-provenance is expected and not a risk signal here. | 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
2 findingsMatched 4 signal(s), weighted score 8: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: hzoo, loganfsmyth. • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'loganfsmyth' owns 167 packages, ≥70% share a templated name shape. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared. • [S_TINY_PAYLOAD] Tiny payload: 1 code file(s), 1391 bytes total.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
3 findingsAll 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.
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
3 findingsAll 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.
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.