86%
Total Score
healthy
Active releases and a maintained source repository outweigh workflow pinning and repository-link hygiene gaps.
The organization has two workos.com publishing accounts, but hadihallak uses gmail.com and chancestrickland uses chance.dev; these outside accounts create account-hygiene risk, though organization backing compensates for maintenance capacity concerns.
The linked monorepo name does not match the package and its README does not mention @radix-ui/react-tabs, so package-to-repository ownership is less transparent despite the matching organization.
The repository uses established build and test tooling, but no security-scanning tool was detected; this is a modest transparency gap rather than a severe risk.
No repository security policy was found, leaving vulnerability-reporting expectations unspecified.
All four workflows were analyzed without dangerous sinks or audit findings, and one scopes permissions at job level. However, all 8 action references are unpinned, creating a workflow hygiene and reproducibility gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
@radix-ui/react-id Version 1.1.4 | — | — |
@radix-ui/primitive Version 1.2.0 | — | — |
@radix-ui/react-context Version 1.3.0 | — | — |
@radix-ui/react-presence Version 1.1.11 | — | — |
@radix-ui/react-direction Version 1.2.0 | — | — |
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.