← Home

stream-browserify

npm Repository Homepage

the stream module from node core for browsers

14
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

ahdinosauranandthakkerashaffer88baluptonbpostlethwaitebretcwmmadefunctzombiedominictarrelnounchemilbayesferossforbeslindesayfpereira1garanngkatsevgoto-bus-stophughskindutnyjmmjprichardsonjryansleichtgewichtlukechildsmafintoshmattdeslmaxogdenmellowmelonparshappkruminssethvincentstevemaosubstacktehshriketerinjokesthlorenzungoldmanyerkopalmayoshuawuytszertosh

Keywords

streambrowserbrowserify

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate maintainer transition from substack to stevemao (2015); stevemao is a highly trusted publisher with 1892 approved packages. ai
maintainer-change maintainer-added AI (maintainer-change): feross and stevemao are well-known browserify ecosystem maintainers; addition is a legitimate transfer from 2015. ai

Versions (showing 14 of 14)

Version Deps Published
3.0.0 2 / 4
2.0.2 2 / 3
2.0.1 2 / 2
2.0.0 2 / 2
1.0.0 2 / 2
0.1.3 2 / 2
0.1.2 2 / 2
0.1.1 2 / 2
0.1.0 2 / 2
0.0.4 2 / 0
0.0.3 2 / 0
0.0.2 2 / 0
0.0.1 2 / 0
0.0.0 1 / 0

v2.0.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: stevemao → goto-bus-stop (on 2019-01-22) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-01-22. This could indicate a legitimate maintainer transition or an account compromise.

v2.0.1

2 findings
HIGH Publisher changed: substack → stevemao (on 2015-08-27) provenance

This version was published by a different npm account than previous versions on 2015-08-27. 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.

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.