← Home

babel-plugin-minify-guarded-expressions

npm Repository Homepage

## Example

14
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

babeljsboopathihzoologanfsmythvignesh.shanmugam

Keywords

babel-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): hzoo and loganfsmyth are core Babel project maintainers; spam-publisher flag is a false positive for this official Babel ecosystem package. ai
provenance publisher-changed AI (provenance): hzoo (Henry Zhu) is the Babel project lead; transition from boopathi is a legitimate organizational maintainer change within the Babel team. ai

Versions (showing 14 of 14)

Version Deps Published
0.4.4 2 / 0
0.4.3 1 / 0
0.4.2 1 / 0
0.4.1 1 / 0
0.4.0 1 / 0
0.3.0 1 / 0
0.2.0 1 / 0
0.1.2 1 / 0
0.1.1 1 / 0
0.1.0 1 / 0
0.0.4 1 / 0
0.0.3 1 / 0
0.0.2 1 / 0
0.0.1 1 / 0

v0.4.4

2 findings
HIGH Publisher changed: boopathi → hzoo (on 2019-08-15) provenance

This version was published by a different npm account than previous versions on 2019-08-15. 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.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.2

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

1 finding
LOW No provenance attestation provenance

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

v0.1.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: hzoo → boopathi (on 2017-05-22) provenance

[Accepted risk] 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.

v0.0.4

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: hzoo → kangax (on 2017-01-17) provenance

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

v0.0.3

1 finding
LOW No provenance attestation provenance

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

v0.0.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: amasad → hzoo (on 2016-09-20) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-09-20. This could indicate a legitimate maintainer transition or an account compromise.

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.