@aws-amplify/amplify-app
Amplify CLI
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:yargs | AI (phantom-deps): yargs is declared in dependencies and used via CLI bin; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:rimraf | AI (phantom-deps): rimraf is used in the clean script; phantom-dep heuristic false positive. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): CLI tool legitimately spawns subprocesses for project scaffolding; stable pattern across versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads declared @aws-amplify frontend plugin deps by key; documented plugin-loader pattern. | ai | |
| phantom-deps | phantom-dep:@aws-amplify/amplify-frontend-ios | AI (phantom-deps): Same-org dep loaded dynamically via plugin pattern; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@aws-amplify/amplify-frontend-android | AI (phantom-deps): Same-org dep loaded dynamically via plugin pattern; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.0.48 | 16 / 1 | |
| 5.0.47 | 16 / 1 | |
| 5.0.46 | 16 / 1 | |
| 5.0.45 | 16 / 1 | |
| 5.0.44 | 16 / 1 | |
| 5.0.43 | 16 / 1 |
v5.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.