@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 51 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 |
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.