82%
Total Score
88
89
88
One contributor made about 96% of the 77 recent commits, creating a meaningful concentration risk; two additional contributors were active but contributed very little.
The repository name differs from the package name and its README does not mention this package, so the package-to-repository link is less transparent than ideal; the organization-owned monorepo context partly explains the name mismatch but not the missing mention.
The project uses established build tools and has a build pipeline, but no security-scanning tools were detected, leaving a modest transparency gap.
All 11 workflows were analyzed, all 48 action references are pinned, and no untrusted checkout or script-injection paths were found. However, three workflows grant top-level write access and the audit flags high-confidence use of long-lived publishing credentials.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
chalk Version ^4.1.2 | — | — |
@jest/types Version 30.5.1 | — | — |
graceful-fs Version ^4.2.11 | — | — |
natural-compare Version ^1.4.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.