84%
Total Score
healthy
Active maintenance and strong project backing outweigh unpinned workflow actions and minor publishing-account gaps.
The package is backed by an organization, but two publishing accounts use outside domains: hadihallak (gmail.com) and chancestrickland (chance.dev). This is an account-hygiene caution rather than evidence of limited maintenance capacity.
The repository name does not match the package and its README does not mention @radix-ui/react-direction. Because this can make package-to-source ownership less transparent, it is a caution, although the organization backing and monorepo context provide some compensation.
The repository uses Vitest, TypeScript, Vite, and npm scripts, and it has a working build toolchain. No security scanning tools were detected, leaving a modest security-process gap.
The repository has no security policy. This limits the transparency of vulnerability-reporting and response procedures, though it does not indicate abandonment by itself.
All four workflows were analyzed without high- or medium-severity findings, and no untrusted checkout or script-injection paths were found. However, all 8 action references are unpinned, so their exact code can change over time.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.