Shared utility types.
68%
Total Score
caution
Usable with caveats: active project backing is offset by workflow credential exposure and unclear package-to-repository linkage.
Only one registry account has publish access, which is a concentration risk, though the organization-backed repository provides broader maintenance context.
The repository has substantial open issue and pull request counts, while only four issues closed and no pull requests merged in the last month; this suggests backlog pressure.
The repository name does not match the package and its README does not mention the package, so the package-to-repository relationship is not clearly demonstrated; this could be normal for a monorepo but remains a transparency concern.
The project uses TypeScript, Vitest, Turbo, and npm scripts, but no security scanning tools were detected, leaving a modest security-process gap.
No repository security policy was found, reducing transparency about how vulnerabilities should be reported and handled.
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.