The package is licensed, documented, tested, and backed by a matching repository with recent release work. Release history is sparse, recent commit activity is absent, and all 15 workflow action references are unpinned, so maintenance and build hygiene remain concerns.
68%
Total Score
67
100
89
67
The registry namespace and repository are owned by the same individual account, providing direct ownership alignment but no organizational backing to broaden maintenance capacity.
The package has existed for about 10 years but only has four releases, with a median gap of about 4 years. One release appeared in the last 12 months, so this is a meaningful maintenance concern rather than abandonment evidence by itself.
The repository recorded zero commits and zero active maintainers in the last 3 months. Recent release and pull-request activity partly offsets this, but the current maintenance cadence is still unclear.
The repository has five stars and one fork, showing limited adoption. This is only supporting evidence and does not outweigh the direct maintenance signals.
The repository has no security policy. This is a modest transparency gap for reporting and handling vulnerabilities, not evidence that the package is unsafe.
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.