78%
Total Score
healthy
Active maintenance and provenance offset workflow pinning gaps and a repository that does not identify this package.
The organization-backed project has four registry maintainers, but hadihallak (gmail.com) and chancestrickland (chance.dev) publish outside the workos.com domain; this is an account-hygiene caution, not evidence of limited maintenance capacity.
The repository name does not match the package and its README does not mention @radix-ui/react-popper. Although a monorepo can legitimately host subpackages, this weakens direct transparency about the package’s source.
The repository uses TypeScript, Vite, Vitest, and npm scripts, indicating an established build and test toolchain. No security-scanning tools were detected, leaving a modest security-process gap.
The linked repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.
All four workflows were analyzed with no injection or high-severity findings, and one scopes permissions at job level. However, all eight action references are unpinned, so workflow dependencies can change without a reviewable commit pin.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
@radix-ui/rect Version 1.1.3 | — | — |
@radix-ui/react-arrow Version 1.1.17 | — | — |
@floating-ui/react-dom Version ^2.0.0 | — | — |
@radix-ui/react-context Version 1.3.0 | — | — |
@radix-ui/react-use-rect 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.