← Home

@ardatan/eventsource

npm Repository Homepage

W3C compliant EventSource client for Node.js and browser (polyfill)

2
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

ardatan

Keywords

eventsourcehttpstreamingssepolyfill

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:new-function-constructor AI (semgrep): new Function() usage is in a webpack-bundled browser polyfill (example/eventsource-polyfill.js), a generated artifact from the upstream eventsource repo. Pattern is a standard polyfill technique, not attacker-controlled input. ai
provenance no-provenance AI (provenance): Trusted publisher (ardatan) with strong track record; lack of Sigstore provenance is common and not a meaningful risk signal here. ai

Versions (showing 2 of 2)

Version Deps Published
1.1.2 1 / 8
1.1.1 1 / 8

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.