tree-select ui component for react
79%
Total Score
100
100
89
50
A prepare script runs during installation, adding execution during package setup. No provided evidence shows that it is unsafe, so this is a limited supply-chain hygiene concern rather than a severe risk.
The package has a long history and 270 releases, but there has been no registry release for about 20 months. Active repository commits partly compensate for the stale registry cadence.
The repository name does not match the package name and its README does not mention rc-tree-select, so the linkage is less transparent than expected. The name mismatch could be normal for a related component repository, but the absence of a README mention remains a caution.
No repository security policy was found, leaving vulnerability-reporting expectations less transparent. Existing security scanning partly offsets this documentation gap.
All five workflows were analyzed with no detected high-confidence findings or untrusted checkouts, but three workflows grant top-level write permissions and half of action references are unpinned. These are workflow hygiene concerns without an observed untrusted sink.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
rc-tree Version ~5.13.0 | — | — |
rc-util Version ^5.43.0 | — | — |
rc-select Version ~14.16.2 | — | — |
classnames Version 2.x | — | — |
@babel/runtime Version ^7.25.7 | — | — |
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.