The project has tests, release notes, a clear MIT license, and no install-time scripts. Its small user base, missing security policy, and unpinned workflow actions leave maintenance and build-integrity concerns.
58%
Total Score
33
100
72
75
Only three releases exist, with none in the last 12 months; the latest registry release was over three years ago. This materially raises abandonment risk despite the roughly 16-day median interval during its brief release period.
There were no commits and no active maintainers in the last three months. Combined with the old latest release, this is meaningful evidence of stalled maintenance.
One registry maintainer is listed, matching the individual repository owner. A single maintainer can support a small package, but it leaves limited visible continuity if that maintainer stops responding.
The package and repository are owned by the same individual account, so the source appears aligned with the published package. It also means there is no observed organizational backing to compensate for the single-maintainer and low-activity concerns.
The repository has three stars, no forks, and one watcher. Low adoption is not disqualifying, but it provides little evidence of community testing or support.
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.