← Home

promise.prototype.finally

npm Repository Homepage

ES Proposal spec-compliant shim for Promise.prototype.finally

14
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

ljharbmattandrews

Keywords

Promisepromisesfinallypromise.prototype.finallyES7ES8ES2017shimpolyfilles-shim API

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate maintainer transition from mattandrews to ljharb (2016); ljharb is the canonical es-shims maintainer with extensive track record. ai
maintainer-change maintainer-added AI (maintainer-change): ljharb added as maintainer in 2016; well-known es-shims ecosystem steward with 4000+ approved versions. ai
publish-pattern new-deps-added AI (publish-pattern): define-properties, es-abstract, function-bind are standard es-shims ecosystem deps maintained by ljharb. ai
provenance no-provenance AI (provenance): Package published in 2016, before Sigstore provenance existed. Not actionable. ai

Versions (showing 14 of 14)

Version Deps Published
3.1.8 5 / 10
3.1.7 5 / 10
3.1.5 3 / 10
3.1.4 3 / 10
3.1.3 3 / 8
3.1.2 3 / 7
3.1.1 3 / 7
3.1.0 3 / 8
3.0.1 3 / 8
3.0.0 3 / 8
2.0.1 3 / 8
2.0.0 3 / 8
1.0.1 0 / 4
1.0.0 0 / 4

v3.1.8

1 finding
LOW No provenance attestation provenance

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

v3.1.7

1 finding
LOW No provenance attestation provenance

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

v3.1.5

1 finding
LOW No provenance attestation provenance

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

v3.1.4

1 finding
LOW No provenance attestation provenance

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

v3.1.3

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

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

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
INFO No provenance attestation provenance

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

v2.0.0

2 findings
HIGH Publisher changed: mattandrews → ljharb (on 2016-08-21) provenance

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