@aws-amplify/amplify-category-predictions
amplify-cli predictions plugin
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:aws-sdk | AI (phantom-deps): aws-sdk is a declared runtime dependency in package.json; phantom-dep heuristic is a false positive here. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require resolves to a local provider-utils subdirectory path; stable plugin-dispatch pattern for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.5.27 | 5 / 1 | |
| 5.5.26 | 5 / 1 | |
| 5.5.25 | 5 / 1 | |
| 5.5.24 | 5 / 1 | |
| 5.5.23 | 5 / 1 | |
| 5.5.22 | 6 / 1 |
v5.5.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.