babel-preset-env MIT 11 versions

babel-preset-env

npm Repository Homepage

A Babel preset for each environment.

11

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

danezexistentialismhzoologanfsmythsebmckthejameskyle

Versions (showing 11 of 11)

Version	Deps	Published
1.7.0	30 / 19	2018-05-10
1.5.2	30 / 19	2017-06-07
1.5.0	30 / 19	2017-05-20
1.3.3	29 / 20	2017-04-07
1.3.1	29 / 20	2017-03-30
1.2.1	30 / 16	2017-03-06
1.1.10	30 / 16	2017-02-24
1.1.9	30 / 16	2017-02-24
1.1.5	28 / 14	2017-01-04
0.0.5	28 / 13	2016-10-13
0.0.1	37 / 10	2016-09-06

v1.7.0

2 findings

HIGH Publisher changed: danez → existentialism (on 2018-05-10) provenance

This version was published by a different npm account than previous versions on 2018-05-10. 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.

v1.5.2

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.3.3

1 finding

LOW No provenance attestation provenance

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

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.1.10

1 finding

LOW No provenance attestation provenance

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

v1.1.9

1 finding

LOW No provenance attestation provenance

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

v1.1.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.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.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.