Usable with caveats: the package is licensed, stable, tested in its source repository, and has a long release history. However, it has had no registry release for about 12 months and no commits in the last 3 months, while the linked repository does not clearly identify this package.
64%
Total Score
75
100
88
67
The package has 42 releases over about two years, but there have been no releases in roughly 12 months despite a previously rapid cadence. That is a meaningful maintenance concern.
The repository recorded zero commits and zero active maintainers in the last 3 months, indicating currently paused development and increasing abandonment risk.
The repository name does not match the package name and its README does not mention the package, so the linkage is not clearly established and deserves verification before adoption.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This is a transparency gap, but not by itself evidence that the package is unsafe.
The only workflow lacks top-level token permissions, so its permissions are not explicitly constrained at workflow scope.
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.