promise-polyfill
Lightweight promise polyfill. A+ compliant
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 |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/polyfill.js | AI (source-diff): UMD bundle of Promise polyfill; factory pattern and setTimeout trigger false positive. No actual network calls. | ai | |
| source-diff | net-exec-file:lib/polyfill.js | AI (source-diff): CJS build of Promise polyfill; standard promise implementation code, no network activity. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 8.3.0 | 0 / 20 | |
| 8.2.1 | 0 / 20 | |
| 8.2.0 | 0 / 20 | |
| 8.1.3 | 0 / 20 | |
| 8.1.0 | 0 / 18 | |
| 7.1.2 | 0 / 16 | |
| 7.1.1 | 0 / 16 | |
| 7.1.0 | 0 / 16 | |
| 7.0.2 | 0 / 16 | |
| 7.0.1 | 0 / 16 | |
| 7.0.0 | 0 / 16 | |
| 6.1.0 | 0 / 9 | |
| 6.0.2 | 0 / 9 | |
| 6.0.1 | 0 / 9 | |
| 6.0.0 | 0 / 9 | |
| 5.2.1 | 0 / 9 | |
| 5.2.0 | 0 / 9 | |
| 5.1.0 | 0 / 9 | |
| 5.0.0 | 0 / 9 | |
| 4.0.4 | 0 / 9 | |
| 4.0.3 | 0 / 9 | |
| 4.0.2 | 0 / 9 | |
| 4.0.1 | 0 / 9 | |
| 3.1.0 | 0 / 4 | |
| 3.0.0 | 0 / 4 | |
| 2.1.4 | 0 / 4 | |
| 2.1.3 | 0 / 4 | |
| 2.1.2 | 0 / 4 | |
| 2.1.1 | 0 / 4 | |
| 2.1.0 | 0 / 4 | |
| 2.0.2 | 0 / 3 | |
| 2.0.1 | 0 / 3 | |
| 2.0.0 | 0 / 3 | |
| 1.1.6 | 0 / 3 | |
| 1.1.5 | 0 / 3 | |
| 1.1.3 | 0 / 3 | |
| 1.1.2 | 0 / 3 | |
| 1.1.0 | 0 / 1 | |
| 1.0.6 | 0 / 1 | |
| 1.0.5 | 0 / 1 | |
| 1.0.1 | 0 / 1 |
v8.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.