rc-dialog
dialog 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): Both zombiej and afc163 are known Ant Design / react-component team members; legitimate maintainer rotation within the org. | ai |
Versions (showing 100 of 162)
| Version | Deps | Published |
|---|---|---|
| 10.0.0 | 5 / 34 | |
| 9.6.0 | 5 / 34 | |
| 9.5.2 | 5 / 33 | |
| 9.5.1 | 5 / 33 | |
| 9.5.0 | 5 / 33 | |
| 9.4.0 | 5 / 33 | |
| 9.3.4 | 5 / 33 | |
| 9.3.3 | 5 / 33 | |
| 9.3.2 | 5 / 33 | |
| 9.3.1 | 5 / 33 | |
| 9.3.0 | 5 / 33 | |
| 9.2.0 | 5 / 33 | |
| 9.1.0 | 5 / 33 | |
| 9.0.4 | 5 / 32 | |
| 9.0.3 | 5 / 32 | |
| 9.0.2 | 5 / 32 | |
| 9.0.1 | 5 / 32 | |
| 9.0.0 | 5 / 31 | |
| 8.9.0 | 4 / 29 | |
| 8.8.2 | 4 / 29 | |
| 8.8.1 | 4 / 29 | |
| 8.8.0 | 4 / 29 | |
| 8.7.0 | 4 / 29 | |
| 8.6.0 | 4 / 29 | |
| 8.5.3 | 4 / 29 | |
| 8.5.2 | 4 / 29 | |
| 8.5.1 | 4 / 29 | |
| 8.5.0 | 4 / 29 | |
| 8.4.6 | 4 / 29 | |
| 8.4.5 | 4 / 29 | |
| 8.4.4 | 4 / 25 | |
| 8.4.3 | 4 / 25 | |
| 8.4.2 | 4 / 25 | |
| 8.4.1 | 4 / 25 | |
| 8.4.0 | 4 / 24 | |
| 8.3.4 | 3 / 23 | |
| 8.3.3 | 3 / 23 | |
| 8.3.2 | 3 / 23 | |
| 8.3.1 | 3 / 23 | |
| 8.3.0 | 3 / 23 | |
| 8.2.2 | 3 / 22 | |
| 8.2.1 | 3 / 22 | |
| 8.2.0 | 3 / 22 | |
| 8.1.2 | 2 / 15 | |
| 8.1.1 | 2 / 15 | |
| 8.1.0 | 2 / 15 | |
| 8.0.1 | 3 / 15 | |
| 8.0.0 | 3 / 15 | |
| 7.7.0 | 3 / 15 | |
| 7.6.1 | 3 / 15 | |
| 7.6.0 | 3 / 15 | |
| 7.5.14 | 3 / 15 | |
| 7.5.13 | 3 / 15 | |
| 7.5.12 | 3 / 15 | |
| 7.5.11 | 3 / 15 | |
| 7.5.10 | 3 / 15 | |
| 7.5.9 | 3 / 15 | |
| 7.5.8 | 3 / 15 | |
| 7.5.7 | 3 / 15 | |
| 7.5.6 | 3 / 15 | |
| 7.5.5 | 3 / 15 | |
| 7.5.4 | 3 / 15 | |
| 7.5.3 | 3 / 15 | |
| 7.5.2 | 3 / 15 | |
| 7.5.1 | 3 / 15 | |
| 7.5.0 | 3 / 15 | |
| 7.4.1 | 3 / 14 | |
| 7.4.0 | 3 / 14 | |
| 7.3.1 | 3 / 14 | |
| 7.3.0 | 3 / 14 | |
| 7.2.1 | 3 / 14 | |
| 7.2.0 | 3 / 14 | |
| 7.1.8 | 3 / 14 | |
| 7.1.7 | 3 / 14 | |
| 7.1.6 | 3 / 14 | |
| 7.1.4 | 3 / 14 | |
| 7.1.3 | 3 / 14 | |
| 7.1.2 | 3 / 14 | |
| 7.1.1 | 3 / 14 | |
| 7.1.0 | 5 / 14 | |
| 7.0.4 | 5 / 14 | |
| 7.0.3 | 5 / 14 | |
| 7.0.2 | 5 / 14 | |
| 7.0.1 | 5 / 14 | |
| 7.0.0 | 5 / 14 | |
| 6.5.11 | 5 / 16 | |
| 6.5.10 | 5 / 16 | |
| 6.5.9 | 5 / 15 | |
| 6.5.8 | 4 / 16 | |
| 6.5.7 | 4 / 16 | |
| 6.5.6 | 4 / 16 | |
| 6.5.5 | 4 / 16 | |
| 6.5.4 | 4 / 16 | |
| 6.5.3 | 4 / 16 | |
| 6.5.2 | 4 / 16 | |
| 6.5.1 | 4 / 16 | |
| 6.5.0 | 4 / 16 | |
| 6.4.5 | 4 / 16 | |
| 6.4.4 | 4 / 12 | |
| 6.4.3 | 4 / 12 |
v9.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.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 2024-06-04. This could indicate a legitimate maintainer transition or an account compromise.
v9.5.0
2 findingsThis version was published by a different npm account than previous versions on 2024-05-28. 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.
v9.4.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-02-29. This could indicate a legitimate maintainer transition or an account compromise.
v9.3.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 2023-10-20. This could indicate a legitimate maintainer transition or an account compromise.
v9.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.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-08-08. This could indicate a legitimate maintainer transition or an account compromise.
v9.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 2023-03-01. This could indicate a legitimate maintainer transition or an account compromise.
v9.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.3
2 findingsThis version was published by a different npm account than previous versions on 2024-08-01. 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.
v9.0.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 2022-10-30. This could indicate a legitimate maintainer transition or an account compromise.
v9.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.