rc-collapse
rc-collapse 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): zombiej is a long-standing maintainer in the ant-design/react-component org, same team as afc163. Legitimate maintainer rotation. | ai |
Versions (showing 84 of 84)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 4 / 25 | |
| 3.9.0 | 4 / 24 | |
| 3.8.0 | 4 / 23 | |
| 3.7.3 | 4 / 23 | |
| 3.7.2 | 4 / 21 | |
| 3.7.1 | 4 / 21 | |
| 3.7.0 | 4 / 21 | |
| 3.6.0 | 4 / 21 | |
| 3.5.2 | 4 / 21 | |
| 3.5.1 | 4 / 19 | |
| 3.5.0 | 4 / 19 | |
| 3.4.2 | 5 / 22 | |
| 3.4.1 | 5 / 22 | |
| 3.4.0 | 5 / 22 | |
| 3.3.1 | 5 / 20 | |
| 3.3.0 | 5 / 20 | |
| 3.2.0 | 5 / 20 | |
| 3.1.4 | 5 / 20 | |
| 3.1.3 | 5 / 20 | |
| 3.1.2 | 5 / 20 | |
| 3.1.1 | 5 / 20 | |
| 3.1.0 | 5 / 20 | |
| 3.0.1 | 5 / 20 | |
| 3.0.0 | 5 / 20 | |
| 2.1.0 | 6 / 20 | |
| 2.0.1 | 5 / 9 | |
| 2.0.0 | 5 / 9 | |
| 1.11.8 | 7 / 9 | |
| 1.11.7 | 7 / 9 | |
| 1.11.6 | 7 / 9 | |
| 1.11.5 | 6 / 9 | |
| 1.11.4 | 6 / 9 | |
| 1.11.3 | 6 / 9 | |
| 1.11.2 | 6 / 9 | |
| 1.11.1 | 6 / 9 | |
| 1.11.0 | 6 / 9 | |
| 1.10.3 | 6 / 9 | |
| 1.10.2 | 5 / 9 | |
| 1.10.1 | 4 / 9 | |
| 1.10.0 | 4 / 9 | |
| 1.9.3 | 4 / 9 | |
| 1.9.2 | 4 / 9 | |
| 1.9.1 | 4 / 9 | |
| 1.9.0 | 4 / 9 | |
| 1.8.0 | 4 / 9 | |
| 1.7.7 | 4 / 9 | |
| 1.7.6 | 4 / 9 | |
| 1.7.5 | 4 / 9 | |
| 1.7.3 | 4 / 8 | |
| 1.7.2 | 4 / 8 | |
| 1.7.1 | 4 / 8 | |
| 1.7.0 | 4 / 8 | |
| 1.6.12 | 3 / 8 | |
| 1.6.11 | 3 / 8 | |
| 1.6.10 | 3 / 8 | |
| 1.6.9 | 3 / 8 | |
| 1.6.8 | 3 / 8 | |
| 1.6.7 | 3 / 8 | |
| 1.6.6 | 3 / 8 | |
| 1.6.5 | 3 / 8 | |
| 1.6.4 | 3 / 8 | |
| 1.6.3 | 3 / 8 | |
| 1.6.2 | 3 / 8 | |
| 1.6.1 | 3 / 8 | |
| 1.6.0 | 3 / 8 | |
| 1.5.0 | 3 / 9 | |
| 1.4.6 | 3 / 9 | |
| 1.4.5 | 3 / 9 | |
| 1.4.4 | 3 / 8 | |
| 1.4.3 | 3 / 8 | |
| 1.4.2 | 3 / 8 | |
| 1.4.1 | 3 / 8 | |
| 1.4.0 | 3 / 8 | |
| 1.3.2 | 3 / 7 | |
| 1.3.1 | 3 / 6 | |
| 1.3.0 | 2 / 7 | |
| 1.2.7 | 2 / 7 | |
| 1.2.6 | 2 / 7 | |
| 1.2.5 | 2 / 7 | |
| 1.2.4 | 2 / 7 | |
| 1.2.3 | 2 / 7 | |
| 1.2.2 | 2 / 7 | |
| 1.2.1 | 2 / 7 | |
| 1.2.0 | 2 / 6 |
v3.9.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 2024-10-28. This could indicate a legitimate maintainer transition or an account compromise.
v3.8.0
2 findingsThis version was published by a different npm account than previous versions on 2024-08-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.
v3.7.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 2024-03-16. This could indicate a legitimate maintainer transition or an account compromise.
v3.7.2
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.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.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-05-23. This could indicate a legitimate maintainer transition or an account compromise.
v3.6.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-04-14. This could indicate a legitimate maintainer transition or an account compromise.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
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-01-13. This could indicate a legitimate maintainer transition or an account compromise.
v3.5.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-01-12. This could indicate a legitimate maintainer transition or an account compromise.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
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 2022-07-01. This could indicate a legitimate maintainer transition or an account compromise.
v3.3.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 2022-05-27. This could indicate a legitimate maintainer transition or an account compromise.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
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 2022-04-08. This could indicate a legitimate maintainer transition or an account compromise.
v3.1.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 2022-04-08. This could indicate a legitimate maintainer transition or an account compromise.
v3.1.2
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 2021-09-02. This could indicate a legitimate maintainer transition or an account compromise.
v3.1.1
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 2021-05-26. This could indicate a legitimate maintainer transition or an account compromise.
v3.1.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 2020-11-24. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.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 2020-11-16. This could indicate a legitimate maintainer transition or an account compromise.