@aws-amplify/ui-react-core
`@aws-amplify/ui-react-core` is a React platform agnostic utility library for Amplify UI internal usage in `@aws-amplify/ui-react*` and `@aws-amplify/ui-react-native*` namespaced packages.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Major version bump (v2→v3) with significant new functionality; large file count is expected. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): AWS org restructuring; removal of individual/team accounts consistent with org-level consolidation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Major version bump after restructuring; dormancy explained by AWS team reorganization, not takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): react-hook-form is a well-known, widely-used form library pinned to a specific version; low risk. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): AWS org restructuring; aws-amplify-data-runtime is a legitimate AWS team account. | ai | |
| phantom-deps | phantom-dep:xstate | AI (phantom-deps): xstate is declared in dependencies alongside @xstate/react; usage pattern is expected. Not a security concern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): @aws-amplify scoped package from established publisher; inflated semver matches ecosystem versioning; missing metadata is cosmetic. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is declared in dependencies; phantom-dep scanner likely missed transitive/config usage. Not a security concern. | ai |
Versions (showing 51 of 75)
| Version | Deps | Published |
|---|---|---|
| 3.6.4 | 5 / 0 | |
| 3.6.3 | 5 / 0 | |
| 3.6.2 | 5 / 0 | |
| 3.6.1 | 5 / 0 | |
| 3.6.0 | 5 / 0 | |
| 3.5.0 | 5 / 0 | |
| 3.4.7 | 5 / 0 | |
| 3.4.6 | 5 / 0 | |
| 3.4.5 | 5 / 0 | |
| 3.4.4 | 5 / 0 | |
| 3.4.3 | 5 / 0 | |
| 3.4.2 | 5 / 0 | |
| 3.4.1 | 5 / 0 | |
| 3.4.0 | 5 / 0 | |
| 3.3.5 | 5 / 0 | |
| 3.3.4 | 5 / 0 | |
| 3.3.3 | 5 / 0 | |
| 3.3.2 | 5 / 0 | |
| 3.3.1 | 5 / 0 | |
| 3.3.0 | 5 / 0 | |
| 3.2.1 | 5 / 0 | |
| 3.2.0 | 5 / 0 | |
| 3.1.2 | 5 / 0 | |
| 3.1.1 | 5 / 0 | |
| 3.1.0 | 5 / 0 | |
| 3.0.30 | 5 / 0 | |
| 3.0.29 | 5 / 0 | |
| 3.0.28 | 5 / 0 | |
| 3.0.27 | 5 / 0 | |
| 3.0.26 | 5 / 0 | |
| 3.0.25 | 5 / 1 | |
| 3.0.24 | 5 / 0 | |
| 3.0.23 | 5 / 0 | |
| 3.0.22 | 5 / 0 | |
| 3.0.21 | 5 / 0 | |
| 3.0.20 | 5 / 0 | |
| 3.0.19 | 5 / 0 | |
| 3.0.18 | 5 / 0 | |
| 3.0.17 | 5 / 0 | |
| 3.0.16 | 5 / 0 | |
| 3.0.15 | 5 / 0 | |
| 3.0.14 | 5 / 0 | |
| 3.0.13 | 5 / 0 | |
| 3.0.12 | 5 / 0 | |
| 3.0.11 | 5 / 0 | |
| 3.0.10 | 5 / 0 | |
| 3.0.9 | 5 / 0 | |
| 3.0.8 | 5 / 0 | |
| 3.0.7 | 5 / 0 | |
| 3.0.6 | 5 / 0 | |
| 3.0.5 | 5 / 0 |
v3.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.