@vxe-ui/core
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped UI library @vxe-ui/core; not a typosquat of cors — different namespace and purpose entirely. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Standard webpack runtime globalThis polyfill pattern; not user-controlled input. | ai |
Versions (showing 100 of 117)
| Version | Deps | Published |
|---|---|---|
| 4.4.18 | 2 / 32 | |
| 4.4.17 | 2 / 32 | |
| 4.4.16 | 2 / 32 | |
| 4.4.15 | 2 / 32 | |
| 4.4.14 | 2 / 32 | |
| 4.4.13 | 2 / 32 | |
| 4.4.12 | 2 / 30 | |
| 4.4.11 | 2 / 30 | |
| 4.4.10 | 2 / 30 | |
| 4.4.9 | 2 / 30 | |
| 4.4.8 | 2 / 30 | |
| 4.4.7 | 2 / 30 | |
| 4.4.6 | 2 / 30 | |
| 4.4.5 | 2 / 30 | |
| 4.4.4 | 2 / 30 | |
| 4.4.3 | 2 / 30 | |
| 4.4.2 | 2 / 30 | |
| 4.4.1 | 2 / 30 | |
| 4.4.0 | 2 / 30 | |
| 4.3.1 | 2 / 30 | |
| 4.3.0 | 2 / 30 | |
| 4.2.21 | 2 / 30 | |
| 4.2.20 | 2 / 30 | |
| 4.2.19 | 2 / 30 | |
| 4.2.18 | 2 / 30 | |
| 4.2.17 | 2 / 30 | |
| 4.2.16 | 2 / 30 | |
| 4.2.15 | 2 / 30 | |
| 4.2.14 | 2 / 30 | |
| 4.2.13 | 2 / 30 | |
| 4.2.12 | 2 / 30 | |
| 4.2.11 | 2 / 30 | |
| 4.2.10 | 2 / 30 | |
| 4.2.9 | 2 / 30 | |
| 4.2.8 | 2 / 30 | |
| 4.2.6 | 2 / 30 | |
| 4.2.5 | 2 / 30 | |
| 4.2.3 | 2 / 30 | |
| 4.2.2 | 2 / 30 | |
| 4.2.1 | 2 / 30 | |
| 4.2.0 | 2 / 30 | |
| 4.1.5 | 2 / 30 | |
| 4.1.4 | 2 / 30 | |
| 4.1.3 | 2 / 30 | |
| 4.1.2 | 2 / 30 | |
| 4.1.1 | 2 / 30 | |
| 4.1.0 | 2 / 30 | |
| 4.0.39 | 2 / 30 | |
| 4.0.38 | 2 / 30 | |
| 4.0.37 | 2 / 30 | |
| 4.0.36 | 2 / 30 | |
| 4.0.35 | 2 / 30 | |
| 4.0.34 | 2 / 30 | |
| 4.0.33 | 2 / 30 | |
| 4.0.32 | 2 / 30 | |
| 4.0.31 | 2 / 30 | |
| 4.0.30 | 2 / 30 | |
| 4.0.29 | 2 / 30 | |
| 4.0.28 | 2 / 30 | |
| 4.0.27 | 2 / 30 | |
| 4.0.26 | 2 / 30 | |
| 4.0.25 | 2 / 30 | |
| 4.0.24 | 2 / 30 | |
| 4.0.23 | 2 / 30 | |
| 4.0.22 | 2 / 30 | |
| 4.0.21 | 2 / 30 | |
| 4.0.20 | 2 / 30 | |
| 4.0.19 | 2 / 30 | |
| 4.0.18 | 2 / 30 | |
| 4.0.17 | 2 / 30 | |
| 4.0.16 | 2 / 30 | |
| 4.0.15 | 2 / 30 | |
| 4.0.14 | 2 / 30 | |
| 4.0.13 | 2 / 30 | |
| 4.0.12 | 2 / 30 | |
| 4.0.11 | 2 / 30 | |
| 4.0.10 | 2 / 30 | |
| 4.0.9 | 2 / 30 | |
| 4.0.8 | 2 / 30 | |
| 4.0.7 | 2 / 30 | |
| 4.0.6 | 2 / 30 | |
| 4.0.5 | 2 / 30 | |
| 4.0.4 | 2 / 32 | |
| 4.0.3 | 2 / 32 | |
| 4.0.2 | 2 / 32 | |
| 4.0.1 | 2 / 32 | |
| 4.0.0 | 2 / 32 | |
| 3.4.18 | 2 / 31 | |
| 3.4.17 | 2 / 31 | |
| 3.4.16 | 2 / 31 | |
| 3.4.15 | 2 / 31 | |
| 3.4.14 | 2 / 31 | |
| 3.4.13 | 2 / 31 | |
| 3.4.12 | 2 / 31 | |
| 3.4.11 | 2 / 31 | |
| 3.4.10 | 2 / 31 | |
| 3.4.9 | 2 / 31 | |
| 3.4.8 | 2 / 31 | |
| 3.4.7 | 2 / 31 | |
| 3.4.6 | 2 / 31 |
v4.4.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.