@spinajs/orm-sqlite
framework orm sql-lite language module
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:luxon | AI (phantom-deps): luxon is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@spinajs/log | AI (phantom-deps): Same-org dep used transitively; stable false positive for spinajs packages. | ai | |
| phantom-deps | phantom-dep:typescript-mix | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 100 of 419)
| Version | Deps | Published |
|---|---|---|
| 2.0.374 | 10 / 1 | |
| 2.0.373 | 10 / 1 | |
| 2.0.372 | 10 / 1 | |
| 2.0.371 | 10 / 1 | |
| 2.0.370 | 10 / 1 | |
| 2.0.369 | 10 / 1 | |
| 2.0.368 | 10 / 1 | |
| 2.0.367 | 10 / 1 | |
| 2.0.363 | 10 / 1 | |
| 2.0.362 | 10 / 1 | |
| 2.0.361 | 10 / 1 | |
| 2.0.360 | 10 / 1 | |
| 2.0.359 | 10 / 1 | |
| 2.0.358 | 10 / 1 | |
| 2.0.357 | 10 / 1 | |
| 2.0.355 | 10 / 1 | |
| 2.0.354 | 10 / 1 | |
| 2.0.353 | 10 / 1 | |
| 2.0.352 | 10 / 1 | |
| 2.0.351 | 10 / 1 | |
| 2.0.350 | 10 / 1 | |
| 2.0.349 | 10 / 1 | |
| 2.0.348 | 10 / 1 | |
| 2.0.347 | 10 / 1 | |
| 2.0.346 | 10 / 1 | |
| 2.0.345 | 10 / 1 | |
| 2.0.344 | 10 / 1 | |
| 2.0.343 | 10 / 1 | |
| 2.0.342 | 10 / 1 | |
| 2.0.340 | 10 / 1 | |
| 2.0.339 | 10 / 1 | |
| 2.0.337 | 10 / 1 | |
| 2.0.335 | 10 / 1 | |
| 2.0.334 | 10 / 1 | |
| 2.0.333 | 10 / 1 | |
| 2.0.332 | 10 / 1 | |
| 2.0.331 | 10 / 1 | |
| 2.0.330 | 10 / 1 | |
| 2.0.329 | 10 / 1 | |
| 2.0.328 | 10 / 1 | |
| 2.0.327 | 10 / 1 | |
| 2.0.325 | 10 / 1 | |
| 2.0.324 | 10 / 1 | |
| 2.0.323 | 10 / 1 | |
| 2.0.322 | 10 / 1 | |
| 2.0.321 | 10 / 1 | |
| 2.0.320 | 10 / 1 | |
| 2.0.319 | 10 / 1 | |
| 2.0.318 | 10 / 1 | |
| 2.0.317 | 10 / 1 | |
| 2.0.316 | 10 / 1 | |
| 2.0.315 | 10 / 1 | |
| 2.0.314 | 10 / 1 | |
| 2.0.313 | 10 / 1 | |
| 2.0.312 | 10 / 1 | |
| 2.0.311 | 10 / 1 | |
| 2.0.310 | 10 / 1 | |
| 2.0.309 | 10 / 1 | |
| 2.0.308 | 10 / 1 | |
| 2.0.306 | 10 / 1 | |
| 2.0.305 | 10 / 1 | |
| 2.0.304 | 10 / 1 | |
| 2.0.303 | 10 / 1 | |
| 2.0.302 | 10 / 1 | |
| 2.0.301 | 10 / 1 | |
| 2.0.300 | 10 / 1 | |
| 2.0.299 | 10 / 1 | |
| 2.0.297 | 10 / 1 | |
| 2.0.296 | 10 / 1 | |
| 2.0.295 | 10 / 1 | |
| 2.0.294 | 10 / 1 | |
| 2.0.293 | 10 / 1 | |
| 2.0.292 | 10 / 1 | |
| 2.0.291 | 10 / 1 | |
| 2.0.290 | 10 / 1 | |
| 2.0.289 | 10 / 1 | |
| 2.0.288 | 10 / 1 | |
| 2.0.286 | 10 / 1 | |
| 2.0.285 | 10 / 1 | |
| 2.0.284 | 10 / 1 | |
| 2.0.283 | 10 / 1 | |
| 2.0.282 | 10 / 1 | |
| 2.0.281 | 10 / 1 | |
| 2.0.280 | 10 / 1 | |
| 2.0.279 | 10 / 1 | |
| 2.0.278 | 10 / 1 | |
| 2.0.277 | 10 / 1 | |
| 2.0.276 | 10 / 1 | |
| 2.0.275 | 10 / 1 | |
| 2.0.274 | 10 / 1 | |
| 2.0.273 | 10 / 1 | |
| 2.0.272 | 10 / 1 | |
| 2.0.271 | 10 / 1 | |
| 2.0.270 | 10 / 1 | |
| 2.0.269 | 10 / 1 | |
| 2.0.268 | 10 / 1 | |
| 2.0.267 | 10 / 1 | |
| 2.0.266 | 10 / 1 | |
| 2.0.265 | 10 / 1 | |
| 2.0.264 | 10 / 1 |
v2.0.359
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.358
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.357
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.355
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.354
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.353
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.352
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.351
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.350
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.349
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.348
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.347
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.346
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.345
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.344
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.343
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.342
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.340
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.339
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.337
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.335
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.334
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.333
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.332
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.331
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.330
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.329
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.328
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.327
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.325
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.324
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.323
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.322
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.321
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.320
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.319
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.318
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.317
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.316
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.315
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.314
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.313
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.312
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.311
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.310
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.309
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.308
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.306
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.305
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.304
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.303
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.302
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.301
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.300
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.299
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.297
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.296
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.295
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.294
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.293
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.292
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.291
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.290
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.289
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.288
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.286
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.285
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.284
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.283
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.282
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.281
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.280
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.279
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.278
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.277
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.276
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.275
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.274
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.273
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.272
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.271
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.270
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.269
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.268
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.267
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.266
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.265
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.264
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.