The package has no license and its repository does not identify or mention the package, weakening transparency. It also has no recent commit or issue activity, while the release remains a beta with a very small project footprint.
38%
Total Score
50
50
50
No license is declared, and neither the package nor the linked repository contains a recognized license file. That leaves reuse terms unclear for a dependency.
The six releases were concentrated in January 2019, with no releases in the last 12 months and the latest release more than seven years ago. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, despite not being archived. The absence of current development lowers confidence in ongoing maintenance.
There were no new or closed issues or pull requests in the last month, while three issues and one pull request remain open. This suggests little visible maintenance activity.
The linked repository name does not match the package name, and its README does not mention the package. That raises uncertainty about whether the repository is the package's actual project home.
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.