@ant-design/pro-provider
@ant-design/pro-provider
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a framework-scoped package loaded by convention in Ant Design ecosystem packages; phantom detection is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:rc-util | AI (phantom-deps): rc-util is a standard Ant Design ecosystem dependency referenced in config files; phantom detection is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ant-design/pro-utils | AI (phantom-deps): Same-org dependency from the ant-design/pro-components monorepo; used indirectly/by convention rather than direct import. | ai |
Versions (showing 51 of 148)
| Version | Deps | Published |
|---|---|---|
| 2.16.2 | 6 / 1 | |
| 2.16.1 | 6 / 1 | |
| 2.16.0 | 6 / 1 | |
| 2.15.4 | 6 / 1 | |
| 2.15.3 | 6 / 1 | |
| 2.15.2 | 6 / 1 | |
| 2.15.1 | 6 / 1 | |
| 2.15.0 | 6 / 1 | |
| 2.14.9 | 5 / 1 | |
| 2.14.8 | 5 / 1 | |
| 2.14.7 | 5 / 1 | |
| 2.14.5 | 6 / 1 | |
| 2.14.4 | 6 / 1 | |
| 2.14.3 | 6 / 1 | |
| 2.14.2 | 6 / 1 | |
| 2.14.1 | 5 / 1 | |
| 2.14.0 | 5 / 1 | |
| 2.13.5 | 5 / 1 | |
| 2.13.4 | 5 / 1 | |
| 2.13.3 | 5 / 1 | |
| 2.13.2 | 5 / 1 | |
| 2.13.1 | 5 / 1 | |
| 2.13.0 | 5 / 1 | |
| 2.12.3 | 5 / 1 | |
| 2.12.2 | 5 / 1 | |
| 2.12.1 | 5 / 1 | |
| 2.12.0 | 5 / 1 | |
| 2.11.1 | 5 / 1 | |
| 2.11.0 | 5 / 1 | |
| 2.10.5 | 5 / 1 | |
| 2.10.4 | 5 / 1 | |
| 2.10.3 | 5 / 1 | |
| 2.10.2 | 5 / 1 | |
| 2.10.1 | 5 / 1 | |
| 2.10.0 | 5 / 1 | |
| 2.9.0 | 5 / 1 | |
| 2.8.7 | 5 / 1 | |
| 2.8.6 | 5 / 1 | |
| 2.8.5 | 5 / 1 | |
| 2.8.4 | 5 / 1 | |
| 2.8.3 | 5 / 0 | |
| 2.8.2 | 5 / 0 | |
| 2.8.1 | 5 / 0 | |
| 2.8.0 | 5 / 0 | |
| 2.7.0 | 5 / 0 | |
| 2.6.1 | 5 / 0 | |
| 2.6.0 | 5 / 0 | |
| 2.5.0 | 5 / 0 | |
| 2.4.3 | 5 / 0 | |
| 2.4.2 | 5 / 0 | |
| 2.4.1 | 5 / 0 |
v2.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.5
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.
v2.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.2
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.
v2.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.0
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.