eslint-plugin-promise
Enforce best practices for JavaScript promises
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate transfer to eslint-community GitHub org; eslint-community-bot is the canonical publisher going forward. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): michaeldeboey and eslint-community-bot are the new stewards under the eslint-community org. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): macklinu removal is part of the documented transfer to eslint-community. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 7.3.0 | 1 / 16 | |
| 7.2.1 | 1 / 16 | |
| 7.2.0 | 1 / 16 | |
| 7.1.0 | 0 / 16 | |
| 7.0.0 | 0 / 16 | |
| 6.6.0 | 0 / 16 | |
| 6.5.1 | 0 / 16 | |
| 6.5.0 | 0 / 16 | |
| 6.4.0 | 0 / 16 | |
| 6.3.0 | 0 / 16 | |
| 6.2.0 | 0 / 16 | |
| 6.1.1 | 0 / 13 | |
| 6.1.0 | 0 / 13 | |
| 6.0.1 | 0 / 12 | |
| 6.0.0 | 0 / 12 | |
| 5.2.0 | 0 / 12 | |
| 5.1.1 | 0 / 12 | |
| 5.1.0 | 0 / 12 | |
| 5.0.0 | 0 / 12 | |
| 4.3.1 | 0 / 12 | |
| 4.3.0 | 0 / 12 | |
| 4.2.1 | 0 / 12 | |
| 4.1.1 | 0 / 12 | |
| 4.1.0 | 0 / 12 | |
| 4.0.1 | 0 / 12 | |
| 4.0.0 | 0 / 12 | |
| 3.8.0 | 0 / 16 | |
| 3.7.0 | 0 / 16 | |
| 3.6.0 | 0 / 3 | |
| 3.5.0 | 0 / 3 | |
| 3.4.2 | 0 / 3 | |
| 3.4.1 | 0 / 3 | |
| 3.4.0 | 0 / 3 | |
| 3.3.2 | 0 / 3 | |
| 3.3.1 | 0 / 3 | |
| 3.3.0 | 0 / 3 | |
| 3.2.1 | 0 / 3 | |
| 3.2.0 | 0 / 3 | |
| 3.1.0 | 0 / 3 | |
| 3.0.0 | 0 / 3 | |
| 2.0.1 | 0 / 3 | |
| 2.0.0 | 0 / 3 | |
| 1.3.2 | 0 / 3 | |
| 1.3.1 | 0 / 3 | |
| 1.3.0 | 0 / 3 | |
| 1.2.0 | 0 / 3 | |
| 1.1.0 | 0 / 3 | |
| 1.0.8 | 0 / 3 | |
| 1.0.0 | 0 / 3 |
v7.3.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-04-27. This could indicate a legitimate maintainer transition or an account compromise.
v7.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
2 findingsThis version was published by a different npm account than previous versions on 2022-10-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.