amplify-python-function-runtime-provider
Provides functionality related to functions in Python on AWS
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@aws-amplify/amplify-cli-core | AI (dependencies): Internal AWS Amplify monorepo dependency; stable false positive for this package family. | ai | |
| provenance | no-provenance | AI (provenance): AWS Amplify CLI packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.4.56 | 7 / 3 | |
| 2.4.55 | 7 / 3 | |
| 2.4.54 | 7 / 3 | |
| 2.4.53 | 7 / 3 | |
| 2.4.52 | 7 / 3 |
v2.4.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.