The five-file codebase has no tests, security policy, or license, limiting confidence in maintenance and legal reuse. Its stable version and matching organization repository provide some context, but not enough to offset the long inactivity.
45%
Total Score
50
100
67
67
No license is declared, and neither the package nor the linked repository contains a recognized license file. This creates a real legal barrier to adopting the dependency.
The package has had only three releases, with no release in the last three years; its latest release was in May 2023. This materially raises abandonment risk despite the earlier regular release interval.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package having been inactive since May 2023. That is a significant maintenance concern.
The artifact and repository contain only five files, including two source files and a short README. The small scope limits maintenance complexity, but provides little evidence of project maturity.
The linked repository has no security policy. For a small wrapper this is not decisive alone, but it reduces transparency and leaves no documented vulnerability-reporting process.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.