vxe-table
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): Standard Vue component library bundle; network/exec pattern is from legitimate Vue/DOM APIs, not malware. | ai | |
| source-diff | obfuscated-file:lib/table/src/methods.js | AI (source-diff): Standard Babel-compiled CJS output; long lines are minified bundle, not malicious obfuscation. Stable pattern for this package. | ai | |
| osv | osv:GHSA-89fp-f5mx-748x | AI (osv): Advisory affects v4.x (<=4.8.10); this package is on the v3.x branch, outside the affected range. | ai | |
| provenance | no-provenance | AI (provenance): Established package; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:vxe-pc-ui | AI (dependencies): vxe-pc-ui is the companion library from the same x-extends org; stable co-dependency across all vxe-table versions. | ai |
Versions (showing 51 of 194)
| Version | Deps | Published |
|---|---|---|
| 4.20.6 | 0 / 38 | |
| 4.20.5 | 0 / 38 | |
| 4.20.4 | 0 / 38 | |
| 4.20.3 | 0 / 38 | |
| 4.20.2 | 0 / 38 | |
| 4.20.1 | 0 / 38 | |
| 4.20.0 | 0 / 38 | |
| 4.19.25 | 1 / 38 | |
| 4.19.24 | 1 / 38 | |
| 4.19.23 | 1 / 38 | |
| 4.19.22 | 1 / 38 | |
| 4.19.21 | 1 / 38 | |
| 4.19.20 | 1 / 38 | |
| 4.19.19 | 1 / 38 | |
| 4.19.18 | 1 / 38 | |
| 4.19.17 | 1 / 38 | |
| 4.19.16 | 1 / 38 | |
| 4.19.15 | 1 / 38 | |
| 4.19.14 | 1 / 38 | |
| 4.19.13 | 1 / 38 | |
| 4.19.12 | 1 / 38 | |
| 4.19.11 | 1 / 38 | |
| 4.19.10 | 1 / 38 | |
| 4.19.9 | 1 / 38 | |
| 4.19.8 | 1 / 38 | |
| 4.19.7 | 1 / 38 | |
| 4.19.6 | 1 / 38 | |
| 4.19.5 | 1 / 38 | |
| 4.19.4 | 1 / 38 | |
| 4.19.3 | 1 / 38 | |
| 4.19.2 | 1 / 38 | |
| 4.19.1 | 1 / 36 | |
| 4.19.0 | 1 / 36 | |
| 4.18.15 | 1 / 36 | |
| 4.18.14 | 1 / 36 | |
| 4.18.13 | 1 / 36 | |
| 4.18.12 | 1 / 35 | |
| 4.18.11 | 1 / 35 | |
| 4.18.10 | 1 / 35 | |
| 4.18.9 | 1 / 35 | |
| 4.18.8 | 1 / 35 | |
| 4.18.7 | 1 / 35 | |
| 4.18.6 | 1 / 35 | |
| 4.18.5 | 1 / 35 | |
| 4.18.4 | 1 / 35 | |
| 4.18.3 | 1 / 35 | |
| 4.18.2 | 1 / 35 | |
| 4.18.1 | 1 / 35 | |
| 4.18.0 | 1 / 35 | |
| 4.17.51 | 1 / 36 | |
| 4.17.50 | 1 / 35 |
v4.20.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.10
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.18.9
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.18.8
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.18.7
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.18.6
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.18.5
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.18.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.18.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.18.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.18.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.18.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.17.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.