The README, release notes, and MIT license make integration and redistribution clear. A single maintainer, no tests, and no security policy leave little evidence of ongoing support.
43%
Total Score
50
100
80
75
Only one registry maintainer is listed, limiting apparent publishing continuity. The linked repository is user-owned rather than organization-backed, so there is no provided compensating evidence of a broader maintainer base.
The package has had no release in nearly two years and none in the last 12 months, despite four releases arriving within its first few days. That sharp stop in publishing is a meaningful abandonment concern.
There were no commits and no active maintainers in the last three months. For a library consumers integrate into applications, this provides weak evidence of current maintenance.
The repository is not archived, which keeps it technically open for maintenance, but its last push was nearly two years ago and does not offset the broader inactivity evidence.
The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a transparency gap, though it is less serious than the sustained lack of maintenance activity.
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.