← Home

surge-stream

npm Repository Homepage

JavaScript stream library for publishing to surge.sh

9
Versions
ISC
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

sintaxi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): The added dependency is request as an optional dep — a known, established library. Not a meaningful risk for this package. ai
dependencies unvetted-dep:request AI (dependencies): The 'request' library is a long-standing, widely-used HTTP client. It is deprecated but not malicious; its use here is a pre-existing stable dependency. ai
semgrep semgrep:new-function-constructor AI (semgrep): The new Function reference at lib/stream.js:22 is part of a static HTTP status code handler map, not dynamic code execution. False positive for this package. ai
bogus-package bogus-package AI (bogus-package): Package has 20.5k weekly downloads, a clear description, and a legitimate GitHub repo. Sparse README and missing keywords are quality issues, not security signals. ai

Versions (showing 9 of 9)

Version Deps Published
0.10.1 5 / 0
0.10.0 5 / 0
0.9.0 5 / 0
0.8.0 6 / 0
0.7.0 5 / 0
0.6.2 7 / 0
0.6.0 7 / 0
0.5.1 7 / 2
0.5.0 7 / 2

v0.10.1

1 finding
LOW No provenance attestation provenance

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

v0.10.0

1 finding
LOW No provenance attestation provenance

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

v0.9.0

1 finding
LOW No provenance attestation provenance

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

v0.8.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sintaxi.

LOW No provenance attestation provenance

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

v0.7.0

1 finding
LOW No provenance attestation provenance

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

v0.6.2

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.1

1 finding
LOW No provenance attestation provenance

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

v0.5.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.