← Home

@aws-amplify/ui-vue

npm Repository Homepage

[![@aws-amplify/ui-vue Weekly Downloads stat badge](https://img.shields.io/npm/dw/@aws-amplify/ui-vue?label=Download&logo=Amplify)](https://www.npmjs.com/package/@aws-amplify/ui-vue) [![@aws-amplify/ui-vue version badge](https://img.shields.io/npm/v/@aws-

11
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

amzn-ossaws-amplify-opsamplify-studio-uibuilderamplify-codegenamplify-data-dev-npmaws-amplify-data-runtime

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@xstate/vue AI (dependencies): 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 11 of 11)

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

v4.4.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.