@motech-development/s3-file-operations
A wrapper utility to manage file operations on AWS S3
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 2.3.1 | 3 / 21 | |
| 2.3.0 | 3 / 33 | |
| 2.2.1 | 3 / 33 | |
| 2.2.0 | 3 / 32 | |
| 2.1.0 | 3 / 31 | |
| 2.0.13 | 3 / 30 | |
| 2.0.12 | 3 / 30 | |
| 2.0.11 | 3 / 30 | |
| 2.0.10 | 3 / 30 | |
| 2.0.9 | 3 / 30 | |
| 2.0.8 | 3 / 30 | |
| 2.0.7 | 3 / 30 | |
| 2.0.6 | 3 / 30 | |
| 2.0.5 | 3 / 30 | |
| 2.0.4 | 3 / 29 | |
| 2.0.3 | 3 / 29 | |
| 2.0.2 | 3 / 29 | |
| 2.0.1 | 3 / 29 | |
| 2.0.0 | 3 / 29 |
v2.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.