vxe-pc-ui
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 |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/all.esm.js | AI (source-diff): Large ESM bundle for a Vue component library; sample shows standard component code, not dropper/loader patterns. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 1324 versions; provenance attestation not historically used by this publisher. | ai | |
| dependencies | unvetted-dep:@vxe-ui/core | AI (dependencies): @vxe-ui/core is the project's own core package, stable dependency across all versions. | ai |
Versions (showing 100 of 486)
| Version | Deps | Published |
|---|---|---|
| 4.11.4 | 1 / 35 | |
| 4.11.3 | 1 / 35 | |
| 4.11.2 | 1 / 35 | |
| 4.11.1 | 1 / 35 | |
| 4.11.0 | 1 / 35 | |
| 4.10.50 | 1 / 35 | |
| 4.10.49 | 1 / 35 | |
| 4.10.48 | 1 / 35 | |
| 4.10.47 | 1 / 35 | |
| 4.10.46 | 1 / 35 | |
| 4.10.45 | 1 / 35 | |
| 4.10.44 | 1 / 35 | |
| 4.10.43 | 1 / 35 | |
| 4.10.42 | 1 / 35 | |
| 4.10.41 | 1 / 35 | |
| 4.10.40 | 1 / 35 | |
| 4.10.39 | 1 / 35 | |
| 4.10.38 | 1 / 35 | |
| 4.10.37 | 1 / 35 | |
| 4.10.36 | 1 / 35 | |
| 4.10.35 | 1 / 35 | |
| 4.10.34 | 1 / 35 | |
| 4.10.33 | 1 / 35 | |
| 4.10.32 | 1 / 35 | |
| 4.10.31 | 1 / 35 | |
| 4.10.30 | 1 / 35 | |
| 4.10.29 | 1 / 35 | |
| 4.10.28 | 1 / 35 | |
| 4.10.27 | 1 / 35 | |
| 4.10.26 | 1 / 35 | |
| 4.10.25 | 1 / 35 | |
| 4.10.24 | 1 / 35 | |
| 4.10.23 | 1 / 35 | |
| 4.10.22 | 1 / 35 | |
| 4.10.21 | 1 / 35 | |
| 4.10.20 | 1 / 35 | |
| 4.10.19 | 1 / 35 | |
| 4.10.18 | 1 / 35 | |
| 4.10.17 | 1 / 35 | |
| 4.10.16 | 1 / 35 | |
| 4.10.15 | 1 / 35 | |
| 4.10.14 | 1 / 35 | |
| 4.10.13 | 1 / 35 | |
| 3.16.22 | 1 / 36 | |
| 3.16.21 | 1 / 36 | |
| 3.16.20 | 1 / 36 | |
| 3.16.19 | 1 / 36 | |
| 3.16.18 | 1 / 36 | |
| 3.16.17 | 1 / 36 | |
| 3.16.16 | 1 / 36 | |
| 3.16.15 | 1 / 36 | |
| 3.16.14 | 1 / 36 | |
| 3.16.13 | 1 / 36 | |
| 3.16.12 | 1 / 36 | |
| 3.16.11 | 1 / 36 | |
| 3.16.10 | 1 / 36 | |
| 3.16.9 | 1 / 36 | |
| 3.16.8 | 1 / 36 | |
| 3.16.7 | 1 / 36 | |
| 3.16.6 | 1 / 36 | |
| 3.16.5 | 1 / 36 | |
| 3.16.4 | 1 / 36 | |
| 3.16.3 | 1 / 36 | |
| 3.16.2 | 1 / 36 | |
| 3.16.1 | 1 / 36 | |
| 3.16.0 | 1 / 36 | |
| 3.15.28 | 1 / 36 | |
| 3.15.27 | 1 / 36 | |
| 3.15.26 | 1 / 36 | |
| 3.15.25 | 1 / 36 | |
| 3.15.24 | 1 / 36 | |
| 3.15.23 | 1 / 36 | |
| 3.15.22 | 1 / 36 | |
| 3.15.21 | 1 / 36 | |
| 3.15.20 | 1 / 36 | |
| 3.15.19 | 1 / 36 | |
| 3.15.18 | 1 / 36 | |
| 3.15.17 | 1 / 36 | |
| 3.15.16 | 1 / 36 | |
| 3.15.15 | 1 / 36 | |
| 3.15.14 | 1 / 36 | |
| 3.15.13 | 1 / 36 | |
| 3.15.12 | 1 / 36 | |
| 3.15.11 | 1 / 36 | |
| 3.15.10 | 1 / 36 | |
| 3.15.9 | 1 / 36 | |
| 3.15.8 | 1 / 36 | |
| 3.15.7 | 1 / 36 | |
| 3.15.6 | 1 / 36 | |
| 3.15.5 | 1 / 36 | |
| 3.15.4 | 1 / 36 | |
| 3.15.3 | 1 / 36 | |
| 3.15.2 | 1 / 36 | |
| 3.15.1 | 1 / 36 | |
| 3.15.0 | 1 / 36 | |
| 3.14.40 | 1 / 36 | |
| 3.14.39 | 1 / 36 | |
| 3.14.38 | 1 / 36 | |
| 3.14.37 | 1 / 36 | |
| 3.14.36 | 1 / 36 |
v4.11.4
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.11.3
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.11.2
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.11.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.11.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.
v4.10.50
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.10.49
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.10.48
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.10.47
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.10.46
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.10.45
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.10.44
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.10.43
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.10.42
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.10.41
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.10.40
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.10.39
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.10.38
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.10.37
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.10.36
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.10.35
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.10.34
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.10.33
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.10.32
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.10.31
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.10.30
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.10.29
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.10.28
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.10.27
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.10.26
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.10.25
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.10.24
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.10.23
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.10.22
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.10.21
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.10.20
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.10.19
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.10.18
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.10.17
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.10.16
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.10.15
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.10.14
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.10.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.