@aws-amplify/amplify-console-hosting
cli plugin for AWS Amplify Console hosting
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Internal plugin-loader dispatch by deploy type; stable pattern across versions of this AWS Amplify package. | ai | |
| phantom-deps | phantom-dep:ora | AI (phantom-deps): ora is a declared runtime dependency; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.5.44 | 14 / 0 | |
| 2.5.43 | 14 / 0 | |
| 2.5.42 | 14 / 0 | |
| 2.5.41 | 15 / 0 | |
| 2.5.40 | 15 / 0 | |
| 2.5.39 | 13 / 0 |
v2.5.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.