← Home

babel-plugin-minify-simplify

npm Repository Homepage

> Simplifies code for minification by reducing statements into expressions and making expressions uniform where possible.

19
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
provenance publisher-changed AI (provenance): Legitimate transition from amasad to hzoo (Henry Zhu), both core Babel maintainers. Well-documented project handoff. ai
maintainer-change maintainer-added AI (maintainer-change): hzoo is a long-standing Babel core maintainer; addition is expected for this Babel ecosystem package. ai
provenance no-provenance AI (provenance): Published in 2016, before Sigstore/provenance existed. Not actionable for historical versions. ai

Versions (showing 19 of 19)

Version Deps Published
0.5.1 4 / 0
0.5.0 3 / 0
0.4.3 3 / 0
0.4.2 3 / 0
0.4.1 3 / 0
0.4.0 3 / 0
0.3.0 3 / 0
0.2.0 3 / 0
0.1.2 3 / 0
0.1.1 3 / 0
0.1.0 3 / 0
0.0.8 3 / 0
0.0.7 3 / 0
0.0.6 3 / 0
0.0.5 3 / 0
0.0.4 3 / 0
0.0.3 3 / 0
0.0.2 3 / 0
0.0.1 3 / 0

v0.5.1

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.5.0

1 finding
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

1 finding
LOW No provenance attestation provenance

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

v0.0.8

1 finding
LOW No provenance attestation provenance

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

v0.0.7

2 findings
HIGH Publisher changed: kangax → boopathi (on 2017-02-08) provenance

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

1 finding
LOW No provenance attestation provenance

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

v0.0.5

2 findings
HIGH Publisher changed: hzoo → kangax (on 2016-11-21) provenance

This version was published by a different npm account than previous versions on 2016-11-21. 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.4

1 finding
LOW No provenance attestation provenance

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

v0.0.3

2 findings
HIGH Publisher changed: amasad → hzoo (on 2016-09-20) provenance

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.

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
HIGH Publisher changed: amasad → hzoo (on 2016-08-31) provenance

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