@aws-amplify/cli
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Official AWS Amplify CLI; postinstall fetches the CLI binary — documented and stable pattern for this package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @aws-amplify/cli package; Levenshtein match to 'joi' is a false positive with no plausible impersonation intent. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in binary installer to execute the downloaded CLI binary; expected and benign for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 14.4.0 | 3 / 3 | |
| 14.3.0 | 3 / 3 | |
| 14.2.5 | 3 / 3 | |
| 14.2.4 | 3 / 3 | |
| 14.2.3 | 3 / 3 | |
| 14.1.2 | 3 / 3 | |
| 14.1.0 | 3 / 3 | |
| 14.0.1 | 3 / 3 | |
| 14.0.0 | 3 / 3 |
v14.4.0
2 findingsScript: node ./lib/install.js || echo "failed to install amplify binary"
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.3.0
2 findingsScript: node ./lib/install.js || echo "failed to install amplify binary"
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.2.5
2 findingsScript: node ./lib/install.js || echo "failed to install amplify binary"
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.2.4
2 findingsScript: node ./lib/install.js || echo "failed to install amplify binary"
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.2.3
2 findingsScript: node ./lib/install.js || echo "failed to install amplify binary"
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.1.2
2 findingsScript: node ./lib/install.js || echo "failed to install amplify binary"
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.1.0
2 findingsScript: node ./lib/install.js || echo "failed to install amplify binary"
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.1
2 findingsScript: node ./lib/install.js || echo "failed to install amplify binary"
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.0
2 findingsScript: node ./lib/install.js || echo "failed to install amplify binary"
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.