@ant-design/pro-card
@ant-design/pro-card
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-resize-observer | AI (phantom-deps): Standard antd resize-observer util, likely used in bundled output; not a scannable import issue. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Well-known, widely-used dependency in the antd ecosystem. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Bundled es/ output; dep is used but not textually matched. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped convention dep. | ai | |
| phantom-deps | phantom-dep:omit.js | AI (phantom-deps): Bundled es/ output; dep is used but not textually matched. | ai | |
| phantom-deps | phantom-dep:@ant-design/pro-utils | AI (phantom-deps): Same-org dep, expected. | ai | |
| phantom-deps | phantom-dep:@ant-design/icons | AI (phantom-deps): Same-org dep, expected. | ai | |
| phantom-deps | phantom-dep:rc-util | AI (phantom-deps): Bundled es/ output; dep is used but not textually matched. | ai |
Versions (showing 51 of 112)
| Version | Deps | Published |
|---|---|---|
| 2.10.0 | 8 / 1 | |
| 2.9.9 | 8 / 1 | |
| 2.9.8 | 8 / 1 | |
| 2.9.7 | 8 / 1 | |
| 2.9.6 | 8 / 1 | |
| 2.9.5 | 8 / 1 | |
| 2.9.4 | 8 / 1 | |
| 2.9.3 | 9 / 1 | |
| 2.9.2 | 9 / 1 | |
| 2.9.1 | 9 / 1 | |
| 2.9.0 | 9 / 1 | |
| 2.8.8 | 8 / 1 | |
| 2.8.7 | 8 / 1 | |
| 2.8.6 | 8 / 1 | |
| 2.8.5 | 8 / 1 | |
| 2.8.4 | 8 / 1 | |
| 2.8.3 | 8 / 1 | |
| 2.8.2 | 8 / 1 | |
| 2.8.1 | 8 / 1 | |
| 2.8.0 | 8 / 1 | |
| 2.7.2 | 8 / 1 | |
| 2.7.1 | 8 / 1 | |
| 2.7.0 | 8 / 1 | |
| 2.6.2 | 8 / 1 | |
| 2.6.1 | 8 / 1 | |
| 2.6.0 | 8 / 1 | |
| 2.5.30 | 8 / 1 | |
| 2.5.29 | 8 / 1 | |
| 2.5.28 | 8 / 1 | |
| 2.5.27 | 8 / 1 | |
| 2.5.26 | 8 / 1 | |
| 2.5.25 | 8 / 1 | |
| 2.5.24 | 8 / 1 | |
| 2.5.23 | 8 / 1 | |
| 2.5.22 | 8 / 1 | |
| 2.5.21 | 8 / 1 | |
| 2.5.20 | 8 / 1 | |
| 2.5.19 | 8 / 1 | |
| 2.5.18 | 8 / 1 | |
| 2.5.17 | 8 / 1 | |
| 2.5.16 | 8 / 1 | |
| 2.5.15 | 8 / 1 | |
| 2.5.14 | 8 / 1 | |
| 2.5.13 | 8 / 1 | |
| 2.5.12 | 8 / 1 | |
| 2.5.11 | 8 / 1 | |
| 2.5.10 | 8 / 1 | |
| 2.5.9 | 8 / 1 | |
| 2.5.8 | 8 / 1 | |
| 2.5.7 | 8 / 1 | |
| 2.5.6 | 8 / 1 |
v2.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
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.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.