78%
Total Score
healthy
Strong maintenance and provenance outweigh unpinned workflows and weak package-to-repository identification.
The organization-backed package has four publishing accounts, but hadihallak uses gmail.com and chancestrickland uses chance.dev rather than the primary workos.com domain; these are account-hygiene cautions, not evidence of maintenance capacity.
The repository name does not match the package name and its README does not mention the package, so the package-to-repository relationship is not explicit. The monorepo structure makes a name mismatch ordinary, but the missing README mention remains a transparency caution.
The repository uses Vitest, Vite, TypeScript, and npm scripts, but no security-scanning tools were detected. This is a modest transparency and hygiene gap rather than a severe risk.
No repository security policy was found, leaving vulnerability-reporting expectations unclear.
All four workflows were analyzed without injection or high-severity findings, and one scopes permissions at job level. However, all 8 analyzed action references are unpinned, which weakens build reproducibility and supply-chain hygiene.
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-direction Version 1.2.0 | — | — |
@radix-ui/react-primitive Version 2.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.