@aws-amplify/amplify-category-storage
amplify-cli storage plugin
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): CLI command-loader pattern in aws-amplify/amplify-cli; stable across versions of this package. | ai | |
| dependencies | unvetted-dep:@aws-amplify/amplify-cli-core | AI (dependencies): First-party @aws-amplify dependency; stable for this package. | ai | |
| dependencies | unvetted-dep:@aws-amplify/amplify-prompts | AI (dependencies): First-party @aws-amplify dependency; stable for this package. | ai | |
| dependencies | unvetted-dep:@aws-amplify/amplify-util-import | AI (dependencies): First-party @aws-amplify dependency; stable for this package. | ai | |
| dependencies | unvetted-dep:@aws-amplify/cli-extensibility-helper | AI (dependencies): First-party @aws-amplify dependency; stable for this package. | ai | |
| dependencies | unvetted-dep:@aws-amplify/amplify-environment-parameters | AI (dependencies): First-party @aws-amplify dependency; stable for this package. | ai | |
| dependencies | unvetted-dep:amplify-headless-interface | AI (dependencies): Part of the aws-amplify/amplify-cli ecosystem; stable for this package. | ai | |
| dependencies | unvetted-dep:amplify-util-headless-input | AI (dependencies): Part of the aws-amplify/amplify-cli ecosystem; stable for this package. | ai | |
| dependencies | unvetted-dep:promise-sequential | AI (dependencies): Small utility dependency used in AWS Amplify CLI; no malicious indicators. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 5.5.27 | 17 / 2 | |
| 5.5.26 | 17 / 2 | |
| 5.5.24 | 17 / 2 | |
| 5.5.22 | 16 / 2 | |
| 5.5.21 | 16 / 2 | |
| 5.5.20 | 16 / 2 | |
| 5.5.19 | 16 / 2 | |
| 5.5.18 | 16 / 2 | |
| 5.5.17 | 16 / 2 | |
| 5.5.16 | 16 / 2 | |
| 5.5.15 | 16 / 2 | |
| 5.5.14 | 16 / 2 | |
| 5.5.13 | 16 / 2 | |
| 5.5.12 | 16 / 2 | |
| 5.5.11 | 16 / 2 | |
| 5.5.10 | 16 / 2 |
v5.5.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.