@thi.ng/rstream
Reactive streams & subscription primitives for constructing dataflow graphs / pipelines
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@thi.ng/api | AI (dependencies): Same thi.ng umbrella monorepo; stable sibling dependency pattern across all versions. | ai | |
| dependencies | unvetted-dep:@thi.ng/atom | AI (dependencies): Same thi.ng umbrella monorepo; stable sibling dependency pattern across all versions. | ai | |
| dependencies | unvetted-dep:@thi.ng/arrays | AI (dependencies): Same thi.ng umbrella monorepo; stable sibling dependency pattern across all versions. | ai | |
| dependencies | unvetted-dep:@thi.ng/associative | AI (dependencies): Same thi.ng umbrella monorepo; stable sibling dependency pattern across all versions. | ai | |
| dependencies | unvetted-dep:@thi.ng/transducers | AI (dependencies): Same thi.ng umbrella monorepo; stable sibling dependency pattern across all versions. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 9.5.10 | 8 / 4 | |
| 9.5.9 | 8 / 4 | |
| 9.5.8 | 8 / 4 | |
| 9.5.6 | 8 / 4 | |
| 9.5.5 | 8 / 4 | |
| 9.5.3 | 8 / 4 | |
| 9.5.2 | 8 / 4 | |
| 9.5.1 | 8 / 4 | |
| 9.5.0 | 8 / 4 | |
| 9.4.2 | 8 / 4 | |
| 9.4.1 | 8 / 4 | |
| 9.4.0 | 8 / 4 | |
| 9.3.19 | 8 / 4 | |
| 9.3.18 | 8 / 4 | |
| 9.3.17 | 8 / 4 | |
| 9.3.16 | 8 / 4 | |
| 9.3.15 | 8 / 4 | |
| 9.3.13 | 8 / 4 | |
| 9.3.12 | 8 / 4 | |
| 9.3.11 | 8 / 4 | |
| 9.3.10 | 8 / 4 | |
| 9.3.9 | 8 / 4 | |
| 9.3.8 | 8 / 4 | |
| 9.3.7 | 8 / 4 | |
| 9.3.6 | 8 / 4 | |
| 9.3.5 | 8 / 4 | |
| 9.3.4 | 8 / 4 | |
| 9.3.3 | 8 / 4 | |
| 9.2.43 | 8 / 4 | |
| 9.2.42 | 8 / 4 | |
| 9.2.41 | 8 / 4 | |
| 9.2.40 | 8 / 4 | |
| 9.2.39 | 8 / 4 | |
| 9.2.38 | 8 / 4 | |
| 9.2.37 | 8 / 4 | |
| 9.2.36 | 8 / 4 | |
| 9.2.35 | 8 / 4 | |
| 9.2.34 | 8 / 4 | |
| 9.2.33 | 8 / 4 | |
| 9.2.32 | 8 / 4 | |
| 9.2.31 | 8 / 4 | |
| 9.2.30 | 8 / 4 | |
| 9.2.29 | 8 / 4 | |
| 9.2.28 | 8 / 4 | |
| 9.2.27 | 8 / 4 | |
| 9.2.26 | 8 / 4 | |
| 9.2.25 | 8 / 4 | |
| 9.2.24 | 8 / 4 | |
| 9.2.23 | 8 / 4 | |
| 9.2.22 | 8 / 4 | |
| 9.2.21 | 8 / 4 |
v9.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.