@aws-amplify/ui-vue
[](https://www.npmjs.com/package/@aws-amplify/ui-vue) [: Well-known XState Vue integration; stable dependency for this package across versions. | ai | |
| provenance | no-provenance | AI (provenance): AWS Amplify UI packages consistently lack Sigstore provenance; not a risk signal for this publisher. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate AWS Amplify UI component library; sparse README/keywords are a documentation choice, not spam. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Vue component library bundles deps; phantom-dep heuristic unreliable for this package. | ai | |
| phantom-deps | phantom-dep:@vueuse/core | AI (phantom-deps): Vue component library bundles deps; phantom-dep heuristic unreliable for this package. | ai | |
| phantom-deps | phantom-dep:qrcode | AI (phantom-deps): Vue component library bundles deps; phantom-dep heuristic unreliable for this package. | ai | |
| phantom-deps | phantom-dep:@xstate/vue | AI (phantom-deps): Vue component library bundles deps; phantom-dep heuristic unreliable for this package. | ai |
Versions (showing 56 of 56)
| Version | Deps | Published |
|---|---|---|
| 4.4.4 | 6 / 17 | |
| 4.4.3 | 6 / 17 | |
| 4.4.2 | 6 / 17 | |
| 4.4.1 | 6 / 17 | |
| 4.4.0 | 6 / 17 | |
| 4.3.8 | 6 / 17 | |
| 4.3.7 | 6 / 17 | |
| 4.3.6 | 6 / 17 | |
| 4.3.5 | 6 / 17 | |
| 4.3.4 | 6 / 17 | |
| 4.3.3 | 6 / 17 | |
| 4.3.2 | 6 / 17 | |
| 4.3.1 | 6 / 17 | |
| 4.3.0 | 6 / 17 | |
| 4.2.31 | 6 / 17 | |
| 4.2.30 | 6 / 17 | |
| 4.2.29 | 6 / 17 | |
| 4.2.28 | 6 / 17 | |
| 4.2.27 | 6 / 17 | |
| 4.2.26 | 6 / 17 | |
| 4.2.25 | 6 / 17 | |
| 4.2.24 | 6 / 17 | |
| 4.2.23 | 6 / 17 | |
| 4.2.22 | 6 / 17 | |
| 4.2.21 | 6 / 17 | |
| 4.2.20 | 6 / 17 | |
| 4.2.19 | 6 / 17 | |
| 4.2.18 | 6 / 17 | |
| 4.2.17 | 6 / 17 | |
| 4.2.16 | 6 / 17 | |
| 4.2.15 | 6 / 17 | |
| 4.2.14 | 6 / 17 | |
| 4.2.13 | 6 / 17 | |
| 4.2.12 | 6 / 17 | |
| 4.2.11 | 6 / 17 | |
| 4.2.10 | 6 / 17 | |
| 4.2.9 | 6 / 17 | |
| 4.2.8 | 6 / 17 | |
| 4.2.7 | 6 / 17 | |
| 4.2.6 | 6 / 17 | |
| 4.2.5 | 6 / 17 | |
| 4.2.4 | 6 / 17 | |
| 4.2.3 | 6 / 20 | |
| 4.2.2 | 6 / 20 | |
| 4.2.1 | 6 / 20 | |
| 4.2.0 | 6 / 20 | |
| 4.1.0 | 7 / 20 | |
| 4.0.8 | 7 / 20 | |
| 4.0.7 | 7 / 20 | |
| 4.0.6 | 7 / 20 | |
| 4.0.5 | 7 / 20 | |
| 4.0.4 | 7 / 20 | |
| 4.0.3 | 7 / 20 | |
| 4.0.2 | 7 / 20 | |
| 4.0.1 | 7 / 20 | |
| 4.0.0 | 7 / 20 |
v4.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.