← Home

babel-preset-es2016

Babel preset for all es2016 plugins.

14
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

amasadhzoojmmloganfsmythsebmckthejameskyle

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff source-size-tripled AI (source-diff): Tiny absolute payload; ratio inflation from near-zero baseline is not meaningful for this package. ai
bogus-package bogus-package AI (bogus-package): Legitimate Babel ecosystem preset; low-value signals are false positives for this well-known package. ai
provenance missing-githead AI (provenance): Missing gitHead is consistent with 2016-era npm publish workflows before gitHead was standard; no security implication for this package. ai
provenance publisher-changed AI (provenance): hzoo (Henry Zhu) is a core Babel maintainer; the 2016 transition from ysmood to hzoo is a legitimate org handoff within the Babel project, not a compromise. ai
maintainer-change maintainer-added AI (maintainer-change): hzoo is a well-known Babel core maintainer; addition is a legitimate org transition, not a suspicious takeover. ai
phantom-deps phantom-dep:babel-plugin-transform-exponentiation-operator AI (phantom-deps): This dep is the sole declared dependency and is used in the preset config (index.js). The phantom-dep flag is a false positive for Babel preset config-style usage. ai

Versions (showing 14 of 14)

Version Deps Published
6.24.1 1 / 0
6.11.3 1 / 0
6.11.0 1 / 0
6.0.11 22 / 0
6.0.10 26 / 0
6.0.9 24 / 0
6.0.8 23 / 0
6.0.7 21 / 0
6.0.6 23 / 0
6.0.5 23 / 0
6.0.4 23 / 0
6.0.3 23 / 0
6.0.2 22 / 0
6.0.1 21 / 0

v6.24.1

2 findings
LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hzoo.

v6.11.3

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hzoo.

HIGH Publisher changed: ysmood → hzoo (on 2016-07-13) provenance

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

v6.11.0

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hzoo.

HIGH Publisher changed: ysmood → hzoo (on 2016-06-27) provenance

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

v6.0.11

1 finding
LOW No provenance attestation provenance

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

v6.0.10

1 finding
LOW No provenance attestation provenance

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

v6.0.9

1 finding
LOW No provenance attestation provenance

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

v6.0.8

1 finding
LOW No provenance attestation provenance

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

v6.0.7

1 finding
LOW No provenance attestation provenance

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

v6.0.6

1 finding
LOW No provenance attestation provenance

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

v6.0.5

1 finding
LOW No provenance attestation provenance

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

v6.0.4

1 finding
LOW No provenance attestation provenance

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

v6.0.3

1 finding
LOW No provenance attestation provenance

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

v6.0.2

1 finding
LOW No provenance attestation provenance

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

v6.0.1

1 finding
LOW No provenance attestation provenance

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