rc-select
React Select
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 and zombiej are both long-standing maintainers of the react-component org; this is a routine intra-org publisher rotation. | ai | |
| phantom-deps | phantom-dep:rc-motion | AI (phantom-deps): rc-motion is declared in dependencies and used transitively via the component system; stable false positive. | ai |
Versions (showing 51 of 385)
| Version | Deps | Published |
|---|---|---|
| 14.16.8 | 7 / 25 | |
| 14.16.7 | 7 / 25 | |
| 14.16.6 | 7 / 25 | |
| 14.16.5 | 7 / 25 | |
| 14.16.4 | 7 / 25 | |
| 14.16.3 | 7 / 25 | |
| 14.16.2 | 7 / 25 | |
| 14.16.1 | 7 / 25 | |
| 14.16.0 | 7 / 25 | |
| 14.15.2 | 7 / 25 | |
| 14.15.1 | 7 / 23 | |
| 14.15.0 | 7 / 23 | |
| 14.14.0 | 7 / 23 | |
| 14.13.4 | 7 / 23 | |
| 14.13.3 | 7 / 23 | |
| 14.13.2 | 7 / 23 | |
| 14.13.1 | 7 / 22 | |
| 14.13.0 | 7 / 24 | |
| 14.12.1 | 7 / 24 | |
| 14.12.0 | 7 / 24 | |
| 14.11.0 | 7 / 24 | |
| 14.10.0 | 7 / 21 | |
| 14.9.2 | 7 / 21 | |
| 14.9.1 | 7 / 21 | |
| 14.9.0 | 7 / 21 | |
| 14.8.1 | 7 / 21 | |
| 14.8.0 | 7 / 21 | |
| 14.7.4 | 7 / 21 | |
| 14.7.3 | 7 / 21 | |
| 14.7.2 | 7 / 21 | |
| 14.7.1 | 7 / 21 | |
| 14.7.0 | 7 / 20 | |
| 14.6.0 | 7 / 19 | |
| 14.5.2 | 7 / 19 | |
| 14.5.1 | 7 / 19 | |
| 14.5.0 | 7 / 19 | |
| 14.4.3 | 7 / 19 | |
| 14.4.2 | 7 / 19 | |
| 14.4.1 | 7 / 19 | |
| 14.4.0 | 7 / 19 | |
| 14.3.0 | 7 / 19 | |
| 14.2.2 | 7 / 19 | |
| 14.2.0 | 7 / 19 | |
| 14.1.18 | 7 / 19 | |
| 14.1.17 | 7 / 19 | |
| 14.1.16 | 7 / 19 | |
| 14.1.14 | 7 / 19 | |
| 14.1.13 | 7 / 16 | |
| 14.1.12 | 7 / 16 | |
| 14.1.11 | 7 / 16 | |
| 14.1.10 | 7 / 16 |
v14.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.13.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-03-08. This could indicate a legitimate maintainer transition or an account compromise.
v14.12.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-03-07. This could indicate a legitimate maintainer transition or an account compromise.
v14.12.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-28. This could indicate a legitimate maintainer transition or an account compromise.
v14.11.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-02. This could indicate a legitimate maintainer transition or an account compromise.
v14.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.9.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-10-17. This could indicate a legitimate maintainer transition or an account compromise.
v14.9.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-10-13. This could indicate a legitimate maintainer transition or an account compromise.
v14.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 2023-09-20. This could indicate a legitimate maintainer transition or an account compromise.
v14.8.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-09-02. This could indicate a legitimate maintainer transition or an account compromise.
v14.8.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-23. This could indicate a legitimate maintainer transition or an account compromise.
v14.7.4
2 findingsThis version was published by a different npm account than previous versions on 2023-08-09. 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.
v14.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 2023-08-02. This could indicate a legitimate maintainer transition or an account compromise.
v14.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.7.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-07-25. This could indicate a legitimate maintainer transition or an account compromise.
v14.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.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-07-19. This could indicate a legitimate maintainer transition or an account compromise.
v14.5.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-06-06. This could indicate a legitimate maintainer transition or an account compromise.
v14.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-05-24. This could indicate a legitimate maintainer transition or an account compromise.
v14.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-05-18. This could indicate a legitimate maintainer transition or an account compromise.
v14.4.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-04-10. This could indicate a legitimate maintainer transition or an account compromise.
v14.4.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-03-30. This could indicate a legitimate maintainer transition or an account compromise.
v14.4.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-03-29. This could indicate a legitimate maintainer transition or an account compromise.
v14.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 2023-03-16. This could indicate a legitimate maintainer transition or an account compromise.
v14.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.18
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-07-26. This could indicate a legitimate maintainer transition or an account compromise.
v14.1.17
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-07. This could indicate a legitimate maintainer transition or an account compromise.
v14.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.12
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-09-17. This could indicate a legitimate maintainer transition or an account compromise.
v14.1.11
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-09-01. This could indicate a legitimate maintainer transition or an account compromise.
v14.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.