eventsource-parser
Streaming, source-agnostic EventSource/Server-Sent Events parser
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): Publisher changed from rexxars personal account to GitHub Actions CI/CD with SLSA provenance. Repo URL unchanged. Standard migration to automated publishing. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Stable utility library; 338-day gap is normal. Changes are dev-tooling only, SLSA provenance present, no runtime dep changes. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 0 / 15 | |
| 3.0.8 | 0 / 15 | |
| 3.0.7 | 0 / 15 | |
| 3.0.6 | 0 / 15 | |
| 3.0.5 | 0 / 15 | |
| 3.0.3 | 0 / 15 | |
| 3.0.2 | 0 / 15 | |
| 3.0.1 | 0 / 15 | |
| 3.0.0 | 0 / 15 | |
| 1.1.2 | 0 / 14 |
v3.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.7
2 findingsThis version was published by a different npm account than previous versions on 2026-04-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.