React Select
82%
Total Score
100
100
90
70
50
No registry build attestation or trusted-publisher provenance is present, reducing publication transparency, but this is not by itself evidence that the release is unsafe.
A prepare script runs during installation or package setup, adding some execution-time complexity, but this signal alone does not show dangerous behavior.
The package is mature with 476 releases over more than 11 years, but it has had no registry release in the last 12 months. Recent repository activity partly offsets the stale published cadence.
The repository name differs from rc-select and its README does not mention the package, which creates a package-to-source identity concern. The repository path clearly corresponds to the select component, so this is a limited caution rather than a severe finding.
The repository has no published security policy, leaving vulnerability-reporting guidance less transparent for consumers.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
rc-util Version ^5.16.1 | — | — |
rc-motion Version ^2.0.1 | — | — |
classnames Version 2.x | — | — |
rc-overflow Version ^1.3.1 | — | — |
@babel/runtime Version ^7.10.1 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.