86%
Total Score
healthy
Active releases and repository work make this a strong release; unpinned workflow actions and limited package-to-repository labeling are the main gaps.
The package has four publish-access accounts, with two using the organization domain; the Gmail account hadihallak and outside-domain account chancestrickland create account-hygiene caution, though organizational backing compensates for concerns about publishing continuity.
The repository name does not match the package name and its README does not mention the package, creating a transparency gap even though the organization-backed repository appears to be a monorepo.
The repository uses established build and test tooling including Vitest, Vite, TypeScript, and npm scripts. No security scanning tools were detected, leaving a modest security-process gap.
No repository security policy was found, reducing transparency about vulnerability reporting and response expectations.
All four workflows were analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings, but all 8 action references are unpinned. Missing top-level permissions blocks are not concerning here because one workflow uses job-level permissions and none grant top-level write access.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
@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-use-size Version 1.1.5 | — | — |
@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.