@verii/aws-clients
Set of aws functions and utils used by Verii projects
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@aws-sdk/client-ses | AI (dependencies): Official AWS SDK v3 package maintained by Amazon; expected dependency for an AWS utility library. Not a genuine risk. | ai | |
| dependencies | unvetted-dep:@aws-sdk/client-sns | AI (dependencies): Official AWS SDK v3 package maintained by Amazon; expected dependency for an AWS utility library. Not a genuine risk. | ai | |
| dependencies | unvetted-dep:@aws-sdk/client-sesv2 | AI (dependencies): Official AWS SDK v3 package maintained by Amazon; expected dependency for an AWS utility library. Not a genuine risk. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.1.3 | 11 / 14 | |
| 1.1.2 | 11 / 14 | |
| 1.1.1 | 11 / 14 | |
| 1.1.0 | 11 / 14 | |
| 1.0.9 | 11 / 13 | |
| 1.0.8 | 11 / 13 | |
| 1.0.7 | 11 / 13 | |
| 1.0.6 | 11 / 13 | |
| 1.0.5 | 11 / 13 | |
| 1.0.4 | 11 / 13 | |
| 1.0.3 | 11 / 13 | |
| 1.0.2 | 11 / 13 | |
| 1.0.1 | 11 / 13 | |
| 1.0.0 | 11 / 13 |
v1.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.