79%
Total Score
healthy
Active maintenance and verified publishing outweigh unpinned workflow actions and a repository/package naming mismatch.
The company domain accounts fit the organization-backed project, but hadihallak (gmail.com) and chancestrickland (chance.dev) are outside-domain publishing identities and add account-hygiene risk.
The repository name does not match the package and its README does not mention @radix-ui/react-collection. This may be normal for a monorepo, but the package-to-source relationship is less transparent.
The repository uses established build and test tooling, but no security scanning tools were detected; this is a modest transparency gap rather than a maintenance failure.
No repository security policy was found, leaving vulnerability-reporting guidance unclear despite the project's active maintenance.
All four workflows were analyzed with no untrusted checkouts, script injection, or audit findings, but all 8 action references are unpinned, weakening build reproducibility and action-integrity protection.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
@radix-ui/react-slot Version 1.5.0 | — | — |
@radix-ui/react-context Version 1.3.0 | — | — |
@radix-ui/react-primitive Version 2.2.0 | — | — |
@radix-ui/react-compose-refs Version 1.1.5 | — | — |
@radix-ui/react-use-layout-effect Version 1.1.4 | — | — |
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.