86%
Total Score
88
89
75
100
Although 7 contributors were active, one contributor made about 92.6% of the 3-month commits. Organization backing and continued activity reduce the risk, but this remains a maintenance concentration concern.
The linked repository name does not match the package name and its README does not mention the package, so the package-to-repository relationship is less transparent despite the matching organization namespace.
The repository uses established build tools, but no security-scanning tools were detected; this is a modest transparency and hygiene gap rather than an abandonment signal.
No security policy was found in the repository, leaving vulnerability-reporting guidance unclear.
Nine of 13 workflows lack top-level token permissions, although none declare top-level write access and several use read-only or job-level permissions. The mixed configuration is a minor workflow-hygiene concern.
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.