The project has little visible adoption and no security policy, while its workflows use three unpinned actions. Its license and package-to-repository match are clear, but they do not offset the weak maintenance evidence.
42%
Total Score
0
60
50
Only two releases were published, both on January 28, 2025, with none in the following 20 months. That is strong evidence of a very immature or inactive release process.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the long release gap and indicating no current maintenance activity.
The repository has zero stars and forks and only one watcher. Popularity is not required for a healthy package, but this provides no supporting evidence of community use or review.
No security policy was found in the repository. For a library distributed through a registry, that is a transparency gap because there is no documented path for reporting vulnerabilities.
Version 0.0.2 is not a stable major release, which is consistent with an early-stage package and increases compatibility uncertainty. No prerelease labeling partly reduces that 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.