@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 51 of 160)
| Version | Deps | Published |
|---|---|---|
| 3.21.0 | 18 / 3 | |
| 3.20.1 | 18 / 3 | |
| 3.20.0 | 18 / 3 | |
| 3.19.0 | 18 / 3 | |
| 3.18.6 | 18 / 3 | |
| 3.18.5 | 18 / 3 | |
| 3.18.4 | 18 / 3 | |
| 3.18.3 | 19 / 3 | |
| 3.18.2 | 19 / 3 | |
| 3.18.1 | 19 / 3 | |
| 3.18.0 | 19 / 3 | |
| 3.17.2 | 17 / 2 | |
| 3.17.1 | 17 / 2 | |
| 3.17.0 | 17 / 2 | |
| 3.16.6 | 17 / 2 | |
| 3.16.5 | 17 / 2 | |
| 3.16.4 | 17 / 2 | |
| 3.16.3 | 17 / 2 | |
| 3.16.2 | 17 / 2 | |
| 3.16.1 | 17 / 2 | |
| 3.16.0 | 17 / 2 | |
| 3.15.10 | 17 / 2 | |
| 3.15.9 | 17 / 2 | |
| 3.15.8 | 17 / 2 | |
| 3.15.7 | 17 / 2 | |
| 3.15.6 | 17 / 2 | |
| 3.15.5 | 17 / 2 | |
| 3.15.4 | 17 / 2 | |
| 3.15.3 | 17 / 2 | |
| 3.15.2 | 17 / 2 | |
| 3.15.1 | 17 / 2 | |
| 3.15.0 | 17 / 2 | |
| 3.14.2 | 17 / 2 | |
| 3.14.1 | 17 / 2 | |
| 3.14.0 | 17 / 2 | |
| 3.13.14 | 17 / 2 | |
| 3.13.13 | 17 / 2 | |
| 3.13.12 | 16 / 1 | |
| 3.13.11 | 16 / 1 | |
| 3.13.10 | 16 / 1 | |
| 3.13.9 | 16 / 1 | |
| 3.13.8 | 16 / 1 | |
| 3.13.7 | 16 / 1 | |
| 3.13.6 | 16 / 1 | |
| 3.13.5 | 16 / 1 | |
| 3.13.4 | 16 / 1 | |
| 3.13.3 | 16 / 1 | |
| 3.13.2 | 16 / 1 | |
| 3.13.1 | 16 / 1 | |
| 3.13.0 | 16 / 1 | |
| 3.12.15 | 16 / 1 |
v3.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: chenshuai2144.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.