rc-drawer
drawer 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 react-component/antd maintainers; this is a routine intra-team publish, not a takeover. | ai |
Versions (showing 51 of 119)
| Version | Deps | Published |
|---|---|---|
| 8.0.0 | 5 / 28 | |
| 7.3.0 | 5 / 28 | |
| 7.2.0 | 5 / 28 | |
| 7.1.0 | 5 / 28 | |
| 7.0.0 | 5 / 24 | |
| 6.5.2 | 5 / 22 | |
| 6.5.1 | 5 / 22 | |
| 6.5.0 | 5 / 22 | |
| 6.4.1 | 5 / 22 | |
| 6.4.0 | 5 / 22 | |
| 6.3.0 | 5 / 23 | |
| 6.2.0 | 5 / 23 | |
| 6.1.6 | 5 / 23 | |
| 6.1.5 | 5 / 23 | |
| 6.1.4 | 5 / 23 | |
| 6.1.3 | 5 / 23 | |
| 6.1.2 | 5 / 23 | |
| 6.1.1 | 5 / 23 | |
| 6.1.0 | 5 / 23 | |
| 6.0.3 | 5 / 23 | |
| 6.0.2 | 5 / 23 | |
| 6.0.1 | 5 / 23 | |
| 6.0.0 | 5 / 23 | |
| 5.1.0 | 4 / 23 | |
| 4.4.3 | 3 / 24 | |
| 4.4.2 | 3 / 24 | |
| 4.4.1 | 3 / 24 | |
| 4.4.0 | 3 / 24 | |
| 4.3.1 | 3 / 22 | |
| 4.3.0 | 3 / 22 | |
| 4.2.2 | 3 / 22 | |
| 4.2.1 | 4 / 22 | |
| 4.2.0 | 3 / 22 | |
| 4.1.0 | 3 / 22 | |
| 4.0.1 | 3 / 22 | |
| 4.0.0 | 3 / 22 | |
| 3.2.0 | 2 / 22 | |
| 3.1.3 | 3 / 24 | |
| 3.1.1 | 4 / 24 | |
| 3.1.0 | 4 / 24 | |
| 3.0.2 | 4 / 24 | |
| 3.0.0 | 4 / 24 | |
| 2.1.1 | 4 / 23 | |
| 2.0.9 | 4 / 21 | |
| 2.0.8 | 4 / 21 | |
| 2.0.7 | 4 / 21 | |
| 2.0.6 | 4 / 21 | |
| 2.0.5 | 4 / 21 | |
| 2.0.4 | 4 / 21 | |
| 2.0.3 | 4 / 21 | |
| 2.0.2 | 4 / 21 |
v7.3.0
2 findingsThis version was published by a different npm account than previous versions on 2025-05-30. 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.
v7.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 2024-05-30. This could indicate a legitimate maintainer transition or an account compromise.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.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 2024-01-04. This could indicate a legitimate maintainer transition or an account compromise.