@aws-amplify/amplify-frontend-ios
amplify-cli front-end plugin for xcode projects
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 |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): amplify-xcode is the documented Xcode integration binary for this iOS frontend plugin; expected and stable across versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Standard amplify-cli plugin-loader pattern; stable across all versions of this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.7.17 | 5 / 0 | |
| 3.7.16 | 5 / 0 | |
| 3.7.15 | 5 / 0 | |
| 3.7.14 | 5 / 0 | |
| 3.7.13 | 5 / 0 | |
| 3.7.12 | 5 / 0 | |
| 3.7.11 | 5 / 0 | |
| 3.7.10 | 5 / 0 | |
| 3.7.9 | 5 / 0 | |
| 3.7.8 | 5 / 0 |
v3.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.