The project has a clear README, tests, an MIT license, and a stable release. Its single-maintainer base, absent security policy, and lack of security scanning leave limited evidence of ongoing support.
58%
Total Score
33
100
72
75
Only two releases were published, with none in the last 12 months; the latest release is more than a year old. This is meaningful evidence of stalled maintenance for a young library.
There were no commits and no active maintainers in the last three months, reinforcing the evidence that development has stalled.
Only one registry account has publishing access. That is consistent with a user-owned project, but it leaves little visible redundancy if the maintainer becomes unavailable.
There are no open issues or pull requests and no recent issue or pull-request activity. This is consistent with a quiet project but does not establish active maintenance.
The repository name does not match the package name and its README does not mention the package, so the package-to-source relationship is less clearly established than it should be.
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.