@spinajs/fs-s3
file operations implementation for aws s3 storage
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 |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Hex-to-base64 conversion for AWS S3 ContentMD5 header; standard crypto pattern, not obfuscation. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Lodash declared as runtime dep in spinajs packages; phantom-dep heuristic false positive for this monorepo. | ai | |
| phantom-deps | phantom-dep:@spinajs/log | AI (phantom-deps): Same-org package loaded by DI convention; stable false positive for spinajs packages. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/util-utf8-browser | AI (phantom-deps): AWS SDK utility loaded by framework convention; stable false positive for this package. | ai |
Versions (showing 100 of 105)
| Version | Deps | Published |
|---|---|---|
| 2.0.474 | 12 / 1 | |
| 2.0.473 | 12 / 1 | |
| 2.0.472 | 12 / 1 | |
| 2.0.471 | 12 / 1 | |
| 2.0.470 | 12 / 1 | |
| 2.0.469 | 12 / 1 | |
| 2.0.468 | 12 / 1 | |
| 2.0.467 | 12 / 1 | |
| 2.0.466 | 12 / 1 | |
| 2.0.465 | 12 / 1 | |
| 2.0.464 | 12 / 1 | |
| 2.0.463 | 12 / 1 | |
| 2.0.462 | 12 / 1 | |
| 2.0.461 | 11 / 1 | |
| 2.0.460 | 11 / 1 | |
| 2.0.458 | 11 / 1 | |
| 2.0.457 | 11 / 1 | |
| 2.0.456 | 11 / 1 | |
| 2.0.455 | 11 / 1 | |
| 2.0.454 | 11 / 1 | |
| 2.0.453 | 11 / 1 | |
| 2.0.452 | 11 / 1 | |
| 2.0.451 | 11 / 1 | |
| 2.0.450 | 11 / 1 | |
| 2.0.449 | 11 / 1 | |
| 2.0.448 | 11 / 1 | |
| 2.0.447 | 11 / 1 | |
| 2.0.446 | 11 / 1 | |
| 2.0.445 | 11 / 1 | |
| 2.0.444 | 11 / 1 | |
| 2.0.443 | 11 / 1 | |
| 2.0.442 | 11 / 1 | |
| 2.0.441 | 11 / 1 | |
| 2.0.439 | 11 / 1 | |
| 2.0.438 | 11 / 1 | |
| 2.0.436 | 11 / 1 | |
| 2.0.435 | 11 / 1 | |
| 2.0.434 | 11 / 1 | |
| 2.0.433 | 11 / 1 | |
| 2.0.432 | 11 / 1 | |
| 2.0.431 | 11 / 1 | |
| 2.0.430 | 11 / 1 | |
| 2.0.429 | 11 / 1 | |
| 2.0.428 | 11 / 1 | |
| 2.0.427 | 11 / 1 | |
| 2.0.426 | 11 / 1 | |
| 2.0.425 | 11 / 1 | |
| 2.0.424 | 11 / 1 | |
| 2.0.423 | 11 / 1 | |
| 2.0.422 | 11 / 1 | |
| 2.0.421 | 11 / 1 | |
| 2.0.420 | 11 / 1 | |
| 2.0.419 | 11 / 1 | |
| 2.0.418 | 11 / 1 | |
| 2.0.417 | 11 / 1 | |
| 2.0.416 | 11 / 1 | |
| 2.0.415 | 11 / 1 | |
| 2.0.414 | 11 / 1 | |
| 2.0.413 | 11 / 1 | |
| 2.0.412 | 11 / 1 | |
| 2.0.411 | 11 / 1 | |
| 2.0.409 | 11 / 1 | |
| 2.0.408 | 11 / 1 | |
| 2.0.407 | 11 / 1 | |
| 2.0.406 | 11 / 1 | |
| 2.0.405 | 11 / 1 | |
| 2.0.404 | 11 / 1 | |
| 2.0.403 | 11 / 1 | |
| 2.0.402 | 11 / 1 | |
| 2.0.401 | 11 / 1 | |
| 2.0.400 | 11 / 1 | |
| 2.0.399 | 11 / 1 | |
| 2.0.398 | 11 / 1 | |
| 2.0.397 | 11 / 1 | |
| 2.0.396 | 11 / 1 | |
| 2.0.395 | 10 / 1 | |
| 2.0.394 | 10 / 1 | |
| 2.0.393 | 10 / 1 | |
| 2.0.392 | 10 / 1 | |
| 2.0.391 | 10 / 1 | |
| 2.0.390 | 10 / 1 | |
| 2.0.389 | 10 / 1 | |
| 2.0.387 | 10 / 1 | |
| 2.0.386 | 10 / 1 | |
| 2.0.385 | 10 / 1 | |
| 2.0.384 | 10 / 1 | |
| 2.0.383 | 10 / 1 | |
| 2.0.382 | 10 / 1 | |
| 2.0.381 | 9 / 1 | |
| 2.0.379 | 9 / 1 | |
| 2.0.378 | 9 / 1 | |
| 2.0.377 | 9 / 1 | |
| 2.0.375 | 9 / 1 | |
| 2.0.374 | 9 / 1 | |
| 2.0.373 | 9 / 1 | |
| 2.0.372 | 9 / 1 | |
| 2.0.371 | 9 / 1 | |
| 2.0.370 | 9 / 1 | |
| 2.0.369 | 9 / 1 | |
| 2.0.368 | 9 / 1 |
v2.0.474
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.473
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.472
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.471
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.470
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.469
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.468
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.467
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.466
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.465
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.464
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.463
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.462
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.461
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.460
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.458
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.457
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.456
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.455
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.454
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.453
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.452
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.451
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.450
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.449
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.448
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.447
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.446
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.445
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.443
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.442
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.441
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.439
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.438
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.436
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.435
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.434
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.433
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.431
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.430
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.429
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.428
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.427
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.426
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.425
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.424
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.423
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.422
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.421
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.420
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.419
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.418
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.417
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.416
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.415
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.414
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.413
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.412
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.411
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.409
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.408
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.407
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.406
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.405
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.404
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.403
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.402
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.401
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.400
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.399
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.398
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.397
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.396
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.395
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.394
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.393
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.392
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.391
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.390
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.389
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.387
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.386
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.385
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.384
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.383
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.382
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.381
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.379
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.378
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.377
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.375
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.374
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.373
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.372
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.371
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.370
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.369
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.368
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.