@ant-design/pro-list
🏆 Use Ant Design List 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:rc-util | AI (phantom-deps): Common ant-design internal dep, likely used in bundled build output. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Widely used CSS utility, false positive from bundling. | ai | |
| phantom-deps | phantom-dep:unstated-next | AI (phantom-deps): Small state lib used internally in build output. | ai | |
| phantom-deps | phantom-dep:use-media-antd-query | AI (phantom-deps): Ant-design ecosystem dep, false positive from bundling. | ai | |
| phantom-deps | phantom-dep:rc-resize-observer | AI (phantom-deps): rc-resize-observer is a declared dependency; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ant-design/pro-field | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): dayjs is a declared dependency used transitively; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 51 of 160)
| Version | Deps | Published |
|---|---|---|
| 2.6.10 | 11 / 1 | |
| 2.6.9 | 11 / 1 | |
| 2.6.8 | 11 / 1 | |
| 2.6.7 | 11 / 1 | |
| 2.6.6 | 11 / 1 | |
| 2.6.5 | 11 / 1 | |
| 2.6.4 | 11 / 1 | |
| 2.6.3 | 11 / 1 | |
| 2.6.2 | 11 / 1 | |
| 2.6.1 | 11 / 1 | |
| 2.6.0 | 11 / 1 | |
| 2.5.69 | 10 / 1 | |
| 2.5.68 | 10 / 1 | |
| 2.5.67 | 10 / 1 | |
| 2.5.66 | 10 / 1 | |
| 2.5.65 | 10 / 1 | |
| 2.5.64 | 10 / 1 | |
| 2.5.63 | 10 / 1 | |
| 2.5.62 | 10 / 1 | |
| 2.5.61 | 10 / 1 | |
| 2.5.60 | 10 / 1 | |
| 2.5.59 | 10 / 1 | |
| 2.5.58 | 10 / 1 | |
| 2.5.57 | 10 / 1 | |
| 2.5.56 | 10 / 1 | |
| 2.5.55 | 10 / 1 | |
| 2.5.54 | 10 / 1 | |
| 2.5.53 | 10 / 1 | |
| 2.5.52 | 10 / 1 | |
| 2.5.51 | 10 / 1 | |
| 2.5.50 | 10 / 1 | |
| 2.5.49 | 10 / 1 | |
| 2.5.48 | 10 / 1 | |
| 2.5.47 | 10 / 1 | |
| 2.5.46 | 10 / 1 | |
| 2.5.45 | 10 / 1 | |
| 2.5.44 | 10 / 1 | |
| 2.5.43 | 10 / 1 | |
| 2.5.42 | 10 / 1 | |
| 2.5.41 | 10 / 1 | |
| 2.5.40 | 10 / 1 | |
| 2.5.39 | 10 / 1 | |
| 2.5.38 | 10 / 1 | |
| 2.5.37 | 10 / 1 | |
| 2.5.36 | 10 / 1 | |
| 2.5.35 | 10 / 1 | |
| 2.5.34 | 10 / 1 | |
| 2.5.33 | 10 / 1 | |
| 2.5.32 | 10 / 1 | |
| 2.5.31 | 10 / 1 | |
| 2.5.30 | 10 / 1 |
v2.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.