@thi.ng/rstream-graph
Declarative dataflow graph construction for @thi.ng/rstream
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): Sibling thi.ng/umbrella package; stable ecosystem dependency. | ai | |
| dependencies | unvetted-dep:@thi.ng/atom | AI (dependencies): Sibling thi.ng/umbrella package; stable ecosystem dependency. | ai | |
| dependencies | unvetted-dep:@thi.ng/paths | AI (dependencies): Sibling thi.ng/umbrella package; stable ecosystem dependency. | ai | |
| dependencies | unvetted-dep:@thi.ng/rstream | AI (dependencies): Sibling thi.ng/umbrella package; stable ecosystem dependency. | ai | |
| dependencies | unvetted-dep:@thi.ng/resolve-map | AI (dependencies): Sibling thi.ng/umbrella package; stable ecosystem dependency. | ai | |
| dependencies | unvetted-dep:@thi.ng/transducers | AI (dependencies): Sibling thi.ng/umbrella package; stable ecosystem dependency. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 4.1.230 | 8 / 3 | |
| 4.1.229 | 8 / 3 | |
| 4.1.228 | 8 / 3 | |
| 4.1.226 | 8 / 3 | |
| 4.1.225 | 8 / 3 | |
| 4.1.223 | 8 / 3 | |
| 4.1.222 | 8 / 3 | |
| 4.1.221 | 8 / 3 | |
| 4.1.220 | 8 / 3 | |
| 4.1.219 | 8 / 3 | |
| 4.1.218 | 8 / 3 | |
| 4.1.217 | 8 / 3 | |
| 4.1.216 | 8 / 3 | |
| 4.1.215 | 8 / 3 | |
| 4.1.214 | 8 / 3 | |
| 4.1.213 | 8 / 3 | |
| 4.1.212 | 8 / 3 | |
| 4.1.210 | 8 / 3 | |
| 4.1.209 | 8 / 3 | |
| 4.1.208 | 8 / 3 | |
| 4.1.207 | 8 / 3 | |
| 4.1.206 | 8 / 3 | |
| 4.1.205 | 8 / 3 | |
| 4.1.204 | 8 / 3 | |
| 4.1.203 | 8 / 3 | |
| 4.1.202 | 8 / 3 | |
| 4.1.201 | 8 / 3 | |
| 4.1.200 | 8 / 3 | |
| 4.1.196 | 8 / 3 | |
| 4.1.195 | 8 / 3 | |
| 4.1.194 | 8 / 3 | |
| 4.1.193 | 8 / 3 | |
| 4.1.192 | 8 / 3 | |
| 4.1.191 | 8 / 3 | |
| 4.1.190 | 8 / 3 | |
| 4.1.188 | 8 / 3 | |
| 4.1.187 | 8 / 3 | |
| 4.1.186 | 8 / 3 | |
| 4.1.185 | 8 / 3 | |
| 4.1.184 | 8 / 3 | |
| 4.1.183 | 8 / 3 | |
| 4.1.182 | 8 / 3 | |
| 4.1.181 | 8 / 3 | |
| 4.1.180 | 8 / 3 | |
| 4.1.179 | 8 / 3 | |
| 4.1.178 | 8 / 3 | |
| 4.1.177 | 8 / 3 | |
| 4.1.176 | 8 / 3 | |
| 4.1.175 | 8 / 3 | |
| 4.1.174 | 8 / 3 | |
| 4.1.173 | 8 / 3 |
v4.1.230
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.229
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.228
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.226
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.225
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.223
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.221
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.220
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.219
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.218
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.217
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.216
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.215
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.214
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.213
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.212
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.210
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.209
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.208
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.207
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.206
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.205
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.204
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.203
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.202
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.201
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.200
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.196
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.195
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.194
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.193
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.192
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.191
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.190
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.188
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.187
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.186
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.185
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.184
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.183
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.182
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.181
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.180
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.179
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.178
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.177
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.176
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.175
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.174
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.173
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.