← Home

babel-preset-babili

npm

Babel preset for all minify plugins.

16
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

hzoo

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 well-known Babel core team members, not spam publishers. This is a stable false positive for this package. ai
provenance publisher-changed AI (provenance): Publisher change from boopathi to vignesh.shanmugam occurred in 2017 and is a legitimate Babel team transition. vignesh.shanmugam has 533 approved packages and 0 rejections. ai

Versions (showing 16 of 16)

Version Deps Published
1.0.0 0 / 0
0.1.4 23 / 0
0.1.3 23 / 0
0.1.2 23 / 0
0.1.1 23 / 0
0.1.0 23 / 0
0.0.12 23 / 0
0.0.11 22 / 0
0.0.10 22 / 0
0.0.9 18 / 0
0.0.8 17 / 0
0.0.5 15 / 0
0.0.4 15 / 0
0.0.3 15 / 0
0.0.2 15 / 0
0.0.1 15 / 0

v1.0.0

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.

v0.1.4

2 findings
HIGH Publisher changed: boopathi → vignesh.shanmugam (on 2017-06-20) provenance

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

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

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: kangax → boopathi (on 2017-03-03) provenance

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

v0.0.11

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: kangax → boopathi (on 2017-02-08) provenance

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

v0.0.10

1 finding
LOW No provenance attestation provenance

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

v0.0.9

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 2016-11-22) provenance

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

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

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

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

1 finding
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. Consider requesting the maintainer enable provenance via CI/CD.