es6-promisify
Converts callback-based functions to ES6 Promises
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from digitaldesignlabs org account to mikehall314 personal account is the same maintainer (Mike Hall); occurred in 2018 with no issues since. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; no CI/CD attestation expected for this era of publishing. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 7.0.0 | 0 / 16 | |
| 6.1.1 | 0 / 10 | |
| 6.1.0 | 0 / 10 | |
| 6.0.2 | 0 / 8 | |
| 6.0.1 | 0 / 7 | |
| 6.0.0 | 0 / 7 | |
| 5.0.0 | 1 / 5 | |
| 4.1.0 | 1 / 5 | |
| 4.0.0 | 1 / 5 | |
| 3.0.0 | 1 / 4 | |
| 2.0.0 | 1 / 2 | |
| 1.1.1 | 1 / 1 | |
| 1.1.0 | 1 / 1 | |
| 1.0.2 | 1 / 1 | |
| 1.0.1 | 1 / 1 | |
| 1.0.0 | 1 / 1 | |
| 0.1.0 | 1 / 0 |
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
2 findingsThis version was published by a different npm account than previous versions on 2019-08-27. 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
2 findingsThis version was published by a different npm account than previous versions on 2018-10-20. 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.0
2 findingsThis version was published by a different npm account than previous versions on 2018-01-30. 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.