← Home

sse-channel

npm Repository Homepage
3
Versions
—
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

rexxars

Keywords

ssechannelreal-timeserver-sent-eventshtml5eventsourcemessaging

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:shady-links-raw-ip AI (semgrep): The flagged line is a console.log in an example file printing the localhost address (127.0.0.1). Not an actual HTTP request to a raw IP; stable false positive for this package. ai
phantom-deps phantom-dep:in-publish AI (phantom-deps): in-publish is intentionally used only in the prepublish script as a publish guard; not a phantom dep in any security-relevant sense. ai

Versions (showing 3 of 3)

Version Deps Published
4.0.1 1 / 3
4.0.0 0 / 3
2.0.6 3 / 6

v4.0.1

1 finding
LOW No provenance attestation provenance

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

v4.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.

v2.0.6

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.