Documentation, tests, and a recent release provide a solid baseline. Maintenance has been quiet, and unpinned workflow actions plus no security policy reduce confidence in ongoing stewardship.
70%
Total Score
50
100
88
67
The package and repository are owned by the same individual account, so ownership is clear, but there is no organizational backing shown to broaden maintenance capacity.
The package has existed for over four years with 11 releases, but only one release occurred in the last 12 months and releases are spaced about five months apart, indicating a modest maintenance cadence.
There were no commits and no active maintainers during the last three months, which is a meaningful maintenance concern despite the recent package release and repository push.
The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.
Version v0.2.3 is not a prerelease, although the package remains below a stable major version, so its API maturity is somewhat limited.
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.