event-source-polyfill
A polyfill for http://www.w3.org/TR/eventsource/
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 changed to yaffle (the actual author per GitHub/package.json) in 2015; clearly a legitimate transition for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): yaffle is the original author of the EventSource polyfill; maintainer addition is legitimate and stable. | ai | |
| provenance | no-provenance | AI (provenance): Older package without provenance attestation; no security concern given established trust. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Package is 12 years old with 1.3M weekly downloads and 40 versions. Version 0.0.0 is the legitimate initial release of this well-known EventSource polyfill, not a malicious throwaway. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established polyfill with 1.3M weekly downloads. No deps is expected for a pure JS polyfill; README links reference the W3C spec and related resources, not a phishing link farm. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 1.0.31 | 0 / 3 | |
| 1.0.30 | 0 / 3 | |
| 1.0.29 | 0 / 3 | |
| 1.0.28 | 0 / 3 | |
| 1.0.26 | 0 / 3 | |
| 1.0.25 | 0 / 3 | |
| 1.0.24 | 0 / 3 | |
| 1.0.23 | 0 / 3 | |
| 1.0.22 | 0 / 3 | |
| 1.0.21 | 0 / 3 | |
| 1.0.20 | 0 / 3 | |
| 1.0.19 | 0 / 3 | |
| 1.0.18 | 0 / 3 | |
| 1.0.17 | 0 / 3 | |
| 1.0.16 | 0 / 3 | |
| 1.0.15 | 0 / 3 | |
| 1.0.14 | 0 / 3 | |
| 1.0.12 | 0 / 3 | |
| 1.0.11 | 0 / 3 | |
| 1.0.10 | 0 / 3 | |
| 1.0.9 | 0 / 3 | |
| 1.0.8 | 0 / 3 | |
| 1.0.7 | 0 / 3 | |
| 1.0.5 | 0 / 3 | |
| 1.0.4 | 0 / 3 | |
| 1.0.3 | 0 / 3 | |
| 1.0.1 | 0 / 3 | |
| 1.0.0 | 0 / 3 | |
| 0.0.16 | 0 / 3 | |
| 0.0.15 | 0 / 3 | |
| 0.0.14 | 0 / 3 | |
| 0.0.12 | 0 / 3 | |
| 0.0.11 | 0 / 3 | |
| 0.0.10 | 0 / 3 | |
| 0.0.9 | 0 / 3 | |
| 0.0.7 | 0 / 3 | |
| 0.0.6 | 0 / 2 | |
| 0.0.5 | 0 / 2 | |
| 0.0.1 | 0 / 0 | |
| 0.0.0 | 0 / 0 |
v1.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
2 findingsThis version was published by a different npm account than previous versions on 2015-05-15. 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.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.