@spinajs/http-lazy-file-uploader
Incoming file uploader using queue
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Declared and used via @spinajs framework convention; stable pattern. | ai | |
| phantom-deps | phantom-dep:luxon | AI (phantom-deps): Declared and used via @spinajs framework convention; stable pattern. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Declared and used via @spinajs framework convention; stable pattern. | ai | |
| phantom-deps | phantom-dep:formidable | AI (phantom-deps): Declared and used via @spinajs framework convention; stable pattern. | ai | |
| phantom-deps | phantom-dep:@spinajs/di | AI (phantom-deps): Org-scoped framework dependency; used via DI container convention. | ai | |
| phantom-deps | phantom-dep:@spinajs/fs | AI (phantom-deps): Org-scoped framework dependency; used via DI container convention. | ai | |
| phantom-deps | phantom-dep:@spinajs/util | AI (phantom-deps): Org-scoped framework dependency; used via DI container convention. | ai | |
| phantom-deps | phantom-dep:@spinajs/queue | AI (phantom-deps): Org-scoped framework dependency; used via DI container convention. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): Framework-scoped type definitions; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@spinajs/exceptions | AI (phantom-deps): Org-scoped framework dependency; used via DI container convention. | ai | |
| phantom-deps | phantom-dep:@spinajs/log-common | AI (phantom-deps): Org-scoped framework dependency; used via DI container convention. | ai | |
| phantom-deps | phantom-dep:@spinajs/reflection | AI (phantom-deps): Org-scoped framework dependency; used via DI container convention. | ai | |
| phantom-deps | phantom-dep:@spinajs/configuration | AI (phantom-deps): Org-scoped framework dependency; used via DI container convention. | ai |
Versions (showing 78 of 279)
| Version | Deps | Published |
|---|---|---|
| 2.0.264 | 13 / 4 | |
| 2.0.263 | 13 / 4 | |
| 2.0.262 | 13 / 4 | |
| 2.0.261 | 13 / 4 | |
| 2.0.260 | 13 / 4 | |
| 2.0.259 | 13 / 4 | |
| 2.0.258 | 13 / 4 | |
| 2.0.257 | 13 / 4 | |
| 2.0.256 | 13 / 4 | |
| 2.0.255 | 13 / 4 | |
| 2.0.254 | 13 / 4 | |
| 2.0.253 | 13 / 4 | |
| 2.0.252 | 13 / 4 | |
| 2.0.251 | 13 / 4 | |
| 2.0.250 | 13 / 4 | |
| 2.0.249 | 13 / 4 | |
| 2.0.248 | 13 / 4 | |
| 2.0.247 | 13 / 4 | |
| 2.0.246 | 13 / 4 | |
| 2.0.245 | 13 / 4 | |
| 2.0.244 | 13 / 4 | |
| 2.0.243 | 13 / 4 | |
| 2.0.242 | 13 / 4 | |
| 2.0.241 | 13 / 4 | |
| 2.0.240 | 13 / 4 | |
| 2.0.238 | 13 / 4 | |
| 2.0.237 | 13 / 4 | |
| 2.0.236 | 13 / 4 | |
| 2.0.235 | 13 / 4 | |
| 2.0.234 | 13 / 4 | |
| 2.0.233 | 13 / 4 | |
| 2.0.232 | 13 / 4 | |
| 2.0.231 | 13 / 4 | |
| 2.0.230 | 13 / 4 | |
| 2.0.229 | 13 / 4 | |
| 2.0.228 | 13 / 4 | |
| 2.0.227 | 13 / 4 | |
| 2.0.226 | 13 / 4 | |
| 2.0.225 | 13 / 4 | |
| 2.0.224 | 13 / 4 | |
| 2.0.223 | 13 / 4 | |
| 2.0.222 | 13 / 4 | |
| 2.0.221 | 13 / 4 | |
| 2.0.220 | 13 / 4 | |
| 2.0.219 | 13 / 4 | |
| 2.0.218 | 13 / 4 | |
| 2.0.217 | 13 / 4 | |
| 2.0.216 | 13 / 4 | |
| 2.0.215 | 13 / 4 | |
| 2.0.214 | 13 / 4 | |
| 2.0.213 | 13 / 4 | |
| 2.0.212 | 13 / 4 | |
| 2.0.211 | 13 / 4 | |
| 2.0.210 | 13 / 4 | |
| 2.0.209 | 13 / 4 | |
| 2.0.208 | 13 / 4 | |
| 2.0.207 | 13 / 4 | |
| 2.0.206 | 13 / 4 | |
| 2.0.205 | 13 / 4 | |
| 2.0.204 | 13 / 4 | |
| 2.0.203 | 13 / 4 | |
| 2.0.202 | 13 / 4 | |
| 2.0.201 | 13 / 4 | |
| 2.0.200 | 13 / 4 | |
| 2.0.199 | 13 / 4 | |
| 2.0.198 | 13 / 4 | |
| 2.0.197 | 13 / 4 | |
| 2.0.196 | 13 / 4 | |
| 2.0.195 | 13 / 4 | |
| 2.0.194 | 13 / 4 | |
| 2.0.193 | 13 / 4 | |
| 2.0.192 | 13 / 4 | |
| 2.0.191 | 13 / 4 | |
| 2.0.190 | 13 / 4 | |
| 2.0.189 | 13 / 4 | |
| 2.0.188 | 13 / 4 | |
| 2.0.187 | 13 / 4 | |
| 2.0.186 | 13 / 4 |
v2.0.264
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.263
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.262
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.261
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.260
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.259
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.258
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.257
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.256
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.255
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.254
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.253
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.252
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.251
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.250
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.249
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.248
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.247
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.246
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.245
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.244
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.243
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.242
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.241
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.240
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.238
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.237
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.236
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.235
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.234
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.233
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.232
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.231
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.230
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.229
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.228
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.227
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.226
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.225
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.224
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.223
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.222
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.221
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.220
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.219
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.218
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.217
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.216
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.215
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.214
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.213
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.212
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.211
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.210
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.209
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.208
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.207
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.206
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.205
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.204
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.203
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.202
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.201
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.200
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.199
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.198
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.197
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.196
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.195
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.194
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.193
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.192
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.191
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.190
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.189
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.188
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.187
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.186
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.