@aws-amplify/cli-internal
Amplify CLI
5
Versions
Apache-2.0
License
Yes
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
amzn-ossaws-amplify-opsamplify-studio-uibuilderamplify-codegenamplify-data-dev-npmaws-amplify-data-runtime
Keywords
graphqlappsyncaws
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established AWS Amplify monorepo package; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Runs local node scripts/post-install.js; consistent with CLI setup across all versions of this package. | ai | |
| semgrep | semgrep:credential-dir-access | AI (semgrep): Sample shows error message string matching on credential paths, not credential harvesting; stable CLI behavior. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Plugin loader pattern for Amplify provider plugins; documented and stable across versions. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): CLI tool legitimately spawns subprocesses; stable pattern across all versions. | ai |