rc-pagination
pagination ui component for react
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): afc163 is the original antd ecosystem lead and a long-standing maintainer of react-component packages. Transition from madccc is within the same org. | ai |
Versions (showing 51 of 203)
| Version | Deps | Published |
|---|---|---|
| 5.1.0 | 3 / 27 | |
| 5.0.0 | 3 / 27 | |
| 4.3.0 | 3 / 27 | |
| 4.2.0 | 3 / 26 | |
| 4.1.0 | 3 / 26 | |
| 4.0.4 | 3 / 26 | |
| 4.0.3 | 3 / 26 | |
| 4.0.2 | 3 / 28 | |
| 4.0.1 | 3 / 28 | |
| 4.0.0 | 3 / 29 | |
| 3.7.0 | 3 / 26 | |
| 3.6.1 | 3 / 24 | |
| 3.6.0 | 3 / 24 | |
| 3.5.0 | 3 / 24 | |
| 3.4.2 | 2 / 24 | |
| 3.3.1 | 2 / 24 | |
| 3.3.0 | 2 / 24 | |
| 3.2.0 | 2 / 24 | |
| 3.1.17 | 2 / 23 | |
| 3.1.16 | 2 / 22 | |
| 3.1.15 | 2 / 22 | |
| 3.1.14 | 2 / 22 | |
| 3.1.13 | 2 / 22 | |
| 3.1.12 | 2 / 22 | |
| 3.1.11 | 2 / 22 | |
| 3.1.10 | 2 / 22 | |
| 3.1.9 | 2 / 22 | |
| 3.1.8 | 2 / 22 | |
| 3.1.7 | 2 / 22 | |
| 3.1.6 | 2 / 22 | |
| 3.1.4 | 2 / 20 | |
| 3.1.3 | 2 / 20 | |
| 3.1.2 | 2 / 20 | |
| 3.1.1 | 2 / 20 | |
| 3.1.0 | 2 / 20 | |
| 3.0.4 | 2 / 20 | |
| 3.0.3 | 2 / 20 | |
| 3.0.2 | 2 / 20 | |
| 3.0.1 | 2 / 20 | |
| 3.0.0 | 2 / 20 | |
| 2.4.6 | 2 / 20 | |
| 2.4.5 | 2 / 20 | |
| 2.4.4 | 2 / 20 | |
| 2.4.3 | 2 / 20 | |
| 2.4.2 | 2 / 20 | |
| 2.4.1 | 2 / 20 | |
| 2.4.0 | 2 / 20 | |
| 2.3.0 | 2 / 20 | |
| 2.2.5 | 2 / 20 | |
| 2.2.4 | 2 / 20 | |
| 2.2.2 | 1 / 20 |
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
2 findingsThis version was published by a different npm account than previous versions on 2024-05-23. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-12-11. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-11-28. This could indicate a legitimate maintainer transition or an account compromise.