The long release intervals and no commits in the last three months reduce confidence in ongoing maintenance. Organization backing, tests, release notes, licensing, and a small dependency footprint provide useful protection.
70%
Total Score
83
100
93
75
The package has existed for about 9 years but only six releases, with one release in the last 12 months and a median interval of about 12 months. This indicates slow maintenance, though not abandonment by itself.
There were no commits and no active maintainers in the last three months. Combined with the slow release history, this is a real maintenance concern, although the repository was pushed in March 2026.
The repository has no security policy. That limits transparency about vulnerability reporting, but it is a moderate hygiene gap rather than evidence that the release is unsafe to depend on.
All three workflows were analyzed successfully with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, all 13 action references are unpinned, leaving the CI supply chain exposed to moving action versions.
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.