@authing/vue-ui-components
Authing Guard for Vue
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:vue | AI (phantom-deps): vue is a peer/runtime dep for a Vue UI component library; not directly imported in source is expected. | ai |
Versions (showing 51 of 59)
| Version | Deps | Published |
|---|---|---|
| 4.5.54 | 2 / 3 | |
| 4.5.53 | 2 / 3 | |
| 4.5.51 | 2 / 3 | |
| 4.5.50 | 2 / 3 | |
| 4.5.49 | 2 / 3 | |
| 4.5.48 | 2 / 3 | |
| 4.5.47 | 2 / 3 | |
| 4.5.46 | 2 / 3 | |
| 4.5.45 | 2 / 3 | |
| 4.5.44 | 2 / 3 | |
| 4.5.43 | 2 / 3 | |
| 4.5.42 | 2 / 3 | |
| 4.5.41 | 2 / 3 | |
| 4.5.40 | 2 / 3 | |
| 4.5.39 | 2 / 3 | |
| 4.5.37 | 2 / 3 | |
| 4.5.36 | 2 / 3 | |
| 4.5.34 | 2 / 3 | |
| 4.5.33 | 2 / 3 | |
| 4.5.32 | 2 / 3 | |
| 4.5.30 | 2 / 3 | |
| 4.5.29 | 2 / 3 | |
| 4.5.27 | 2 / 3 | |
| 4.5.26 | 2 / 3 | |
| 4.5.25 | 2 / 3 | |
| 4.5.24 | 2 / 3 | |
| 4.5.23 | 2 / 3 | |
| 4.5.22 | 2 / 3 | |
| 4.5.21 | 2 / 3 | |
| 4.5.19 | 2 / 3 | |
| 4.5.18 | 2 / 3 | |
| 4.5.17 | 2 / 3 | |
| 4.5.16 | 2 / 3 | |
| 4.5.14 | 2 / 3 | |
| 4.5.13 | 2 / 3 | |
| 4.5.12 | 2 / 3 | |
| 4.5.10 | 2 / 3 | |
| 4.5.9 | 2 / 3 | |
| 4.5.8 | 2 / 3 | |
| 4.5.7 | 2 / 3 | |
| 4.5.6 | 2 / 3 | |
| 4.5.5 | 2 / 3 | |
| 4.5.4 | 2 / 3 | |
| 4.5.3 | 2 / 3 | |
| 4.5.1 | 2 / 3 | |
| 4.5.0 | 2 / 3 | |
| 4.4.2 | 1 / 48 | |
| 4.4.0 | 1 / 48 | |
| 4.3.10 | 1 / 48 | |
| 4.3.9 | 1 / 48 | |
| 4.3.8 | 1 / 48 |
v4.5.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.