es6-promise MIT 34 versions

es6-promise

npm Repository Homepage

A lightweight library that provides tools for organizing asynchronous code

34

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

jaffathecakestefanpenner

Keywords

futurespolyfillpromisepromises

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Legitimate maintainer transition from Jake Archibald to Stefan Penner, who is a listed author and well-established npm publisher (736 approved packages).	ai	2026/04/24
source-diff	net-exec-file:dist/es6-promise.auto.js	AI (source-diff): UMD bundle of es6-promise polyfill; 'network + exec' is vertx async scheduler + UMD factory pattern, not malware. Stable FP for this package.	ai	2026/04/24

Versions (showing 34 of 34)

Version	Deps	Published
4.2.8	0 / 24	2019-06-06
4.2.7	0 / 24	2019-06-06
4.2.6	0 / 24	2019-02-16
4.2.5	0 / 24	2018-09-10
4.2.4	0 / 24	2018-01-23
4.2.3	0 / 24	2018-01-23
4.2.2	0 / 24	2017-12-22
4.2.1	0 / 24	2017-12-21
4.2.0	0 / 24	2017-12-21
4.1.1	0 / 15	2017-06-28
4.1.0	0 / 15	2017-03-07
4.0.5	0 / 15	2016-10-04
4.0.4	0 / 15	2016-10-03
4.0.3	0 / 15	2016-09-27
4.0.2	0 / 15	2016-09-27
4.0.1	0 / 15	2016-09-27
4.0.0	0 / 15	2016-09-27
3.3.1	0 / 15	2016-09-14
3.3.0	0 / 15	2016-09-12
3.2.1	0 / 15	2016-05-12
3.1.2	0 / 15	2016-02-13
3.0.2	0 / 18	2015-08-10
3.0.1	0 / 18	2015-08-10
3.0.0	0 / 18	2015-08-10
2.3.0	0 / 18	2015-06-10
2.2.0	0 / 18	2015-06-05
2.1.1	0 / 18	2015-04-23
2.1.0	0 / 18	2015-04-15
2.0.1	0 / 23	2014-12-08
2.0.0	0 / 23	2014-10-14
1.0.0	0 / 21	2014-04-28
0.1.2	0 / 21	2014-04-28
0.1.1	0 / 21	2013-12-19
0.1.0	0 / 21	2013-12-16

v4.2.7

1 finding

LOW No provenance attestation provenance

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

v4.2.6

1 finding

LOW No provenance attestation provenance

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

v4.2.5

1 finding

LOW No provenance attestation provenance

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

v4.2.4

1 finding

LOW No provenance attestation provenance

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

v4.2.3

1 finding

LOW No provenance attestation provenance

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

v4.2.2

1 finding

LOW No provenance attestation provenance

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

v4.2.1

1 finding

LOW No provenance attestation provenance

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

v4.2.0

1 finding

LOW No provenance attestation provenance

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

v4.1.1

1 finding

LOW No provenance attestation provenance

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

v4.1.0

1 finding

LOW No provenance attestation provenance

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

v4.0.5

1 finding

LOW No provenance attestation provenance

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

v4.0.4

1 finding

LOW No provenance attestation provenance

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

v4.0.3

1 finding

LOW No provenance attestation provenance

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

v4.0.2

1 finding

LOW No provenance attestation provenance

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

v4.0.1

2 findings

HIGH New file with network + code execution: dist/es6-promise.auto.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v4.0.0

2 findings

HIGH New file with network + code execution: dist/es6-promise.auto.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v3.3.1

1 finding

LOW No provenance attestation provenance

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

v3.3.0

1 finding

LOW No provenance attestation provenance

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

v3.2.1

1 finding

LOW No provenance attestation provenance

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

v3.1.2

1 finding

LOW No provenance attestation provenance

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

v3.0.2

1 finding

LOW No provenance attestation provenance

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

v3.0.1

1 finding

LOW No provenance attestation provenance

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

v3.0.0

2 findings

HIGH Publisher changed: jaffathecake → stefanpenner (on 2015-08-10) provenance

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

1 finding

LOW No provenance attestation provenance

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