78%
Total Score
healthy
Frequent releases and active commits support adoption, but commit ownership is highly concentrated and all workflow actions are unpinned.
The package has four publish-access accounts and is organization-backed through WorkOS, which offsets a thin registry list. The gmail.com and chance.dev accounts are outside the primary workos.com domain, creating some account-hygiene risk.
Commit activity is highly concentrated: one contributor made 106 of 114 commits, or about 93%, even though eight contributors were active. Organization backing provides some handoff capacity but does not remove the concentration risk.
The repository name does not match @radix-ui/react-tabs and its README does not mention the package. This may be normal for a monorepo, but the collected evidence does not directly verify the package mapping.
The project uses Vitest, Vite, TypeScript, and npm scripts, but no security-scanning tools were detected. The build tooling is solid; the missing scanning layer is a modest hygiene gap.
No repository security policy was detected, leaving vulnerability-reporting expectations less transparent for consumers and contributors.
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.