sorted-union-stream
Get the union of two sorted streams
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): Dependency swap from from2/stream-iterate to streamx is a legitimate modernization by the package's own author (mafintosh); streamx is a well-known library in this ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): mafintosh is a long-established, trusted publisher; lack of Sigstore provenance is a process gap, not a security risk for this package. | ai | |
| dependencies | unvetted-dep:streamx | AI (dependencies): streamx is mafintosh's own widely-used streaming library, a legitimate and expected dependency in his ecosystem. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 3.2.3 | 1 / 2 | |
| 3.2.2 | 1 / 2 | |
| 3.2.1 | 1 / 2 | |
| 3.2.0 | 1 / 2 | |
| 3.1.0 | 1 / 2 | |
| 3.0.1 | 1 / 2 | |
| 3.0.0 | 1 / 2 | |
| 2.1.3 | 2 / 2 | |
| 2.1.2 | 2 / 2 | |
| 2.1.1 | 2 / 2 | |
| 2.1.0 | 2 / 2 | |
| 2.0.0 | 1 / 3 | |
| 1.0.2 | 1 / 2 | |
| 1.0.1 | 1 / 2 | |
| 1.0.0 | 1 / 2 | |
| 0.2.5 | 1 / 0 | |
| 0.2.4 | 1 / 0 | |
| 0.2.3 | 0 / 0 | |
| 0.2.2 | 0 / 0 | |
| 0.2.1 | 0 / 0 | |
| 0.2.0 | 0 / 0 | |
| 0.1.0 | 0 / 0 |
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.