← Home

@microsoft/fetch-event-source

npm Repository Homepage

A better API for making Event Source requests, with all the features of fetch()

5
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

microsoft1esvishwambobbybhamravincenzocarusopatobeltran

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): @microsoft scope is org-controlled; vishwam is a long-standing publisher (484 approved, 0 rejected) — legitimate Microsoft team member. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers are Microsoft team members authorized under the @microsoft org scope; normal team changes. ai
bogus-package bogus-package AI (bogus-package): README link density and missing keywords are false positives for a well-established Microsoft package with 2M weekly downloads. ai

Versions (showing 5 of 5)

Version Deps Published
2.0.1 0 / 6
2.0.0 0 / 6
1.0.2 0 / 6
1.0.1 0 / 6
1.0.0 0 / 6

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

2 findings
HIGH Publisher changed: microsoft → vishwam (on 2020-11-18) provenance

This version was published by a different npm account than previous versions on 2020-11-18. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.0

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.