82%
Total Score
healthy
Frequent releases and active repository maintenance outweigh workflow pinning and security-policy gaps.
Most publishing access is associated with workos.com, but hadihallak (gmail.com) and chancestrickland (chance.dev) are outside-domain accounts; this is an account-hygiene caution rather than evidence of limited maintenance capacity.
The repository name does not match the package name and its README does not mention this package, creating some uncertainty about package-to-repository mapping; the monorepo context makes the name mismatch ordinary, but the absent mention remains a caution.
The repository uses Vitest, Vite, TypeScript, and npm scripts, but no security-scanning tools were detected; the build tooling is solid while security-tool coverage is a modest gap.
No repository security policy was found, reducing transparency about vulnerability reporting and response expectations.
All four workflows were analyzed without high-confidence findings or dangerous untrusted triggers, but all 11 action references are unpinned; this is a workflow supply-chain hygiene gap, not a severe risk on its own.
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-slot Version 1.5.0 | — | — |
@radix-ui/react-context Version 1.3.0 | — | — |
@radix-ui/react-presence Version 1.1.11 | — | — |
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.