@aws-amplify/amplify-category-geo
Amplify CLI plugin to manage the Geo resources for the project
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 declared as a runtime dependency in package.json; phantom-dep heuristic is a false positive here. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Provider plugin loader pattern in Amplify CLI; loads named provider plugins by registry key, not user-supplied arbitrary input. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.5.27 | 11 / 0 | |
| 3.5.26 | 11 / 0 | |
| 3.5.25 | 11 / 0 | |
| 3.5.24 | 11 / 0 | |
| 3.5.23 | 11 / 0 | |
| 3.5.22 | 11 / 1 |
v3.5.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.