@ant-design/pro-table
🏆 Use Ant Design Table like a Pro!
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established official package; missing gitHead is publish-env noise, not malicious. | ai | |
| provenance | no-provenance | AI (provenance): No attestation is not a signal on its own for this trusted package. | ai | |
| phantom-deps | phantom-dep:use-media-antd-query | AI (phantom-deps): Responsive hook used by antd components; bundling hides import. | ai | |
| phantom-deps | phantom-dep:react-sortable-hoc | AI (phantom-deps): Used for draggable table rows feature; bundling hides import. | ai | |
| phantom-deps | phantom-dep:use-json-comparison | AI (phantom-deps): Small utility used internally; bundling hides import. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): Core date lib used by pro-table; bundled build hides import text. | ai | |
| phantom-deps | phantom-dep:omit.js | AI (phantom-deps): Standard antd-ecosystem util; false positive from bundling. | ai | |
| phantom-deps | phantom-dep:rc-util | AI (phantom-deps): Common rc-* util dep; false positive from bundling. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Ubiquitous utility dep; false positive from bundling. | ai | |
| phantom-deps | phantom-dep:unstated-next | AI (phantom-deps): Used for state management in pro-table; bundling hides import. | ai | |
| dependencies | unvetted-dep:@ant-design/pro-field | AI (dependencies): Sibling package from the same ant-design/pro-components monorepo; expected dependency, not a risk. | ai | |
| dependencies | unvetted-dep:@ant-design/pro-form | AI (dependencies): Sibling package from the same ant-design/pro-components monorepo; expected dependency, not a risk. | ai |
Versions (showing 60 of 160)
| Version | Deps | Published |
|---|---|---|
| 3.6.4 | 14 / 0 | |
| 3.6.3 | 14 / 0 | |
| 3.6.2 | 14 / 0 | |
| 3.6.1 | 14 / 0 | |
| 3.6.0 | 14 / 0 | |
| 3.5.2 | 14 / 0 | |
| 3.5.1 | 14 / 0 | |
| 3.5.0 | 14 / 0 | |
| 3.4.0 | 14 / 0 | |
| 3.3.2 | 14 / 0 | |
| 3.3.1 | 14 / 0 | |
| 3.3.0 | 14 / 0 | |
| 3.2.14 | 15 / 0 | |
| 3.2.13 | 15 / 0 | |
| 3.2.12 | 15 / 0 | |
| 3.2.11 | 15 / 0 | |
| 3.2.10 | 15 / 0 | |
| 3.2.9 | 15 / 0 | |
| 3.2.8 | 15 / 0 | |
| 3.2.7 | 15 / 0 | |
| 3.2.6 | 15 / 0 | |
| 3.2.5 | 15 / 0 | |
| 3.2.4 | 15 / 0 | |
| 3.2.3 | 15 / 0 | |
| 3.2.2 | 15 / 0 | |
| 3.2.1 | 15 / 0 | |
| 3.2.0 | 15 / 0 | |
| 3.1.9 | 15 / 0 | |
| 3.1.8 | 15 / 0 | |
| 3.1.7 | 15 / 0 | |
| 3.1.6 | 15 / 0 | |
| 3.1.5 | 15 / 0 | |
| 3.1.4 | 15 / 0 | |
| 3.1.3 | 15 / 0 | |
| 3.1.2 | 15 / 0 | |
| 3.1.1 | 15 / 0 | |
| 3.1.0 | 15 / 0 | |
| 3.0.22 | 15 / 0 | |
| 3.0.21 | 15 / 0 | |
| 3.0.20 | 15 / 0 | |
| 3.0.19 | 15 / 0 | |
| 3.0.18 | 15 / 0 | |
| 3.0.17 | 15 / 0 | |
| 3.0.16 | 15 / 0 | |
| 3.0.15 | 15 / 0 | |
| 3.0.14 | 15 / 0 | |
| 3.0.13 | 15 / 0 | |
| 3.0.12 | 15 / 0 | |
| 3.0.11 | 15 / 0 | |
| 3.0.10 | 15 / 0 | |
| 3.0.9 | 15 / 0 | |
| 3.0.8 | 15 / 0 | |
| 3.0.7 | 15 / 0 | |
| 3.0.6 | 15 / 0 | |
| 3.0.5 | 15 / 0 | |
| 3.0.4 | 15 / 0 | |
| 3.0.3 | 15 / 0 | |
| 3.0.2 | 15 / 0 | |
| 3.0.1 | 15 / 0 | |
| 3.0.0 | 15 / 0 |
v3.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.