stream-combiner — Greenflagged

[![npm version](https://img.shields.io/npm/v/stream-combiner.svg)](https://npmjs.org/package/stream-combiner) [![Travis CI](https://travis-ci.org/dominictarr/stream-combiner.svg)](https://travis-ci.org/dominictarr/stream-combiner)

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

dominictarr

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	suspicious-initial-version	AI (npm-metadata): 0.0.0 is the legitimate initial release from ~2012 by established publisher dominictarr; this versioning convention was common in early npm ecosystem and carries no malicious signal here.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance by many years; absence of provenance is expected and not a risk signal for this package.	ai	2026/04/24

Versions (showing 8 of 8)

Version	Deps	Published
0.2.2	2 / 2	2015-06-05
0.2.1	2 / 2	2014-05-29
0.2.0	2 / 2	2014-05-18
0.1.0	2 / 2	2014-05-09
0.0.4	1 / 2	2013-12-11
0.0.2	1 / 2	2013-03-18
0.0.1	1 / 2	2013-01-31
0.0.0	1 / 2	2012-11-27

v0.2.1

1 finding

INFO No provenance attestation provenance

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

v0.2.0

1 finding

INFO No provenance attestation provenance

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