@aws-amplify/ui
`@aws-amplify/ui` contains low-level logic & styles for stand-alone usage or re-use in framework-specific implementations.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/esm/machines/authenticator/actors/resetPassword.mjs | AI (source-diff): Rollup+terser minified output of xstate state machines for auth flows. Legitimate build artifact, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/esm/machines/authenticator/signUp.mjs | AI (source-diff): Rollup+terser minified output of xstate state machines for auth flows. Legitimate build artifact, not obfuscation. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Large official AWS Amplify UI package with many modules; new files are expected across versions. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): aws-amplify-docs-eng-ops is an AWS organizational account; addition is consistent with AWS team restructuring during major version release. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): mlabieniec removal alongside aws-amplify-ops as publisher reflects normal AWS team rotation, not a hostile takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): csstype is a well-known, widely-used CSS type definitions package; legitimate addition for a UI library major version. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is declared as a runtime dependency in package.json and is a standard TypeScript helper; phantom-dep flag is a false positive here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Signals reflect AWS Amplify monorepo publishing patterns (many templated packages, minimal README for sub-packages). Not spam. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): @aws-amplify/ui is an official AWS scoped package, not a typosquat of uuid. Levenshtein distance match is a false positive for scoped packages. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @aws-amplify/ui is an official AWS scoped package, not a typosquat of pg. False positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @aws-amplify/ui is an official AWS scoped package, not a typosquat of qs. False positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @aws-amplify/ui is an official AWS scoped package, not a typosquat of joi. False positive. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @aws-amplify/ui is an official AWS scoped package, not a typosquat of yup. False positive. | ai |
Versions (showing 100 of 362)
| Version | Deps | Published |
|---|---|---|
| 3.12.4 | 3 / 18 | |
| 3.12.3 | 3 / 18 | |
| 3.12.2 | 3 / 18 | |
| 3.12.1 | 3 / 18 | |
| 3.12.0 | 3 / 18 | |
| 3.11.1 | 3 / 18 | |
| 3.11.0 | 3 / 18 | |
| 3.10.1 | 3 / 18 | |
| 3.10.0 | 3 / 18 | |
| 3.9.2 | 3 / 18 | |
| 3.9.1 | 3 / 18 | |
| 3.9.0 | 3 / 18 | |
| 3.8.3 | 3 / 18 | |
| 3.8.2 | 3 / 18 | |
| 3.8.1 | 3 / 18 | |
| 3.8.0 | 3 / 18 | |
| 3.7.0 | 3 / 18 | |
| 3.6.8 | 3 / 18 | |
| 3.6.7 | 3 / 18 | |
| 3.6.6 | 3 / 18 | |
| 3.6.5 | 3 / 18 | |
| 3.6.4 | 3 / 18 | |
| 3.6.3 | 3 / 18 | |
| 3.6.2 | 3 / 18 | |
| 3.6.1 | 3 / 18 | |
| 3.6.0 | 3 / 18 | |
| 3.5.1 | 3 / 18 | |
| 3.5.0 | 3 / 18 | |
| 3.4.1 | 3 / 18 | |
| 3.4.0 | 3 / 18 | |
| 3.3.2 | 3 / 15 | |
| 3.3.1 | 3 / 15 | |
| 3.3.0 | 3 / 15 | |
| 3.2.1 | 3 / 15 | |
| 3.2.0 | 3 / 15 | |
| 3.1.0 | 3 / 15 | |
| 3.0.15 | 3 / 15 | |
| 3.0.14 | 3 / 15 | |
| 3.0.13 | 3 / 15 | |
| 3.0.12 | 3 / 15 | |
| 3.0.11 | 3 / 15 | |
| 3.0.10 | 3 / 15 | |
| 3.0.9 | 3 / 15 | |
| 3.0.8 | 3 / 15 | |
| 3.0.7 | 3 / 15 | |
| 3.0.6 | 3 / 15 | |
| 3.0.5 | 3 / 15 | |
| 3.0.4 | 3 / 15 | |
| 3.0.3 | 3 / 15 | |
| 3.0.2 | 3 / 15 | |
| 3.0.1 | 3 / 15 | |
| 3.0.0 | 3 / 15 | |
| 2.0.7 | 0 / 11 | |
| 2.0.6 | 0 / 11 | |
| 2.0.5 | 0 / 11 | |
| 2.0.4 | 0 / 11 | |
| 2.0.3 | 0 / 11 | |
| 2.0.2 | 0 / 11 | |
| 2.0.1 | 0 / 11 | |
| 1.2.3 | 0 / 11 | |
| 1.1.6 | 0 / 11 | |
| 1.1.5 | 0 / 11 | |
| 1.1.4 | 0 / 11 | |
| 1.1.3 | 0 / 11 | |
| 1.1.2 | 0 / 11 | |
| 1.1.0 | 0 / 11 | |
| 1.0.25 | 0 / 11 | |
| 1.0.24 | 0 / 11 | |
| 1.0.23 | 0 / 11 | |
| 1.0.22 | 0 / 11 | |
| 1.0.20 | 0 / 11 | |
| 1.0.19 | 0 / 19 | |
| 1.0.18 | 0 / 19 | |
| 1.0.17 | 0 / 19 | |
| 1.0.16 | 0 / 18 | |
| 1.0.15 | 0 / 18 | |
| 1.0.14 | 0 / 18 | |
| 1.0.13 | 0 / 18 | |
| 1.0.12 | 0 / 18 | |
| 1.0.11 | 0 / 18 | |
| 1.0.10 | 0 / 18 | |
| 1.0.9 | 0 / 18 | |
| 1.0.8 | 0 / 18 | |
| 1.0.7 | 0 / 18 | |
| 1.0.6 | 0 / 18 | |
| 1.0.5 | 0 / 18 | |
| 1.0.4 | 0 / 18 | |
| 1.0.3 | 0 / 18 | |
| 1.0.2 | 0 / 18 | |
| 1.0.1 | 0 / 18 | |
| 0.0.0-next-fc6e149-20251211181250 | 3 / 7 | |
| 0.0.0-next-f5d5e72-20260311125245 | 3 / 8 | |
| 0.0.0-next-f5bf6fa-20260205153348 | 3 / 8 | |
| 0.0.0-next-f57b0e6-20251119143223 | 3 / 7 | |
| 0.0.0-next-f1561e3-20260112154904 | 3 / 8 | |
| 0.0.0-next-f1561e3-20260112151538 | 3 / 8 | |
| 0.0.0-next-e804e8f-20260303100023 | 3 / 8 | |
| 0.0.0-next-e7dfb41-20260122101400 | 3 / 8 | |
| 0.0.0-next-e51fdca-20260310152830 | 3 / 8 | |
| 0.0.0-next-e45b1fe-20260204143038 | 3 / 8 |
v3.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.