The README is practical, the repository contains tests, and the package has a matching source project. MIT licensing and no install-time scripts help, but the small maintainer base leaves little visible continuity.
56%
Total Score
50
83
75
One registry maintainer is responsible for publishing the package. Because the project is user-owned rather than organization-backed, this leaves a thin maintenance base.
This package has only one release, published nearly four years ago, with no releases in the last 12 months. That indicates limited ongoing maintenance, although a small stable library can remain usable after a complete release.
The repository recorded no commits and no active maintainers in the last three months, consistent with the nearly four-year-old release. This raises abandonment risk despite the repository remaining available.
The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these values provide little external evidence of adoption or review.
The repository has no security policy. That reduces transparency for reporting and handling vulnerabilities, though it is less serious for this small library than for a security-sensitive package.
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.